When Mapping, change the "Ignore" button to mean "Do not create a record for this person but make them a non-constituent record"
D
Damon R. Rosenthal
I feel there is more to this. If this is tied to RE Integration then I don't believe RE NXT (webview) allows a non-constituent primary participant record. The RE database view does. AB only integrates relative to the RE NXT webview interface. AB and BB should find a solution to this where AB can send participant data to a RE Event.
I am still understanding the complexities and some limitation in regards to the RE NXT transition. You can't link to another individual because as Sarita of AB indicates, then all the registration info on a non-constituent record gets linked with that other participant.
If BB is not close to that solution or does not provide AB a path to do within their RE Integration, then provide an interim solution until RE NXT allows non-constituent primary participant records.
Maybe this could be that clients create a RE Almabase Constituent in which AB could have a systematic option to map non-constituent registrations (and their guests) to the that RE Almabase record that would get the desired data into RE Event "Participant" data. That Almabase RE record is not used for anything else other than Event integration.