Event registrant cannot act as host for unnamed guest

A constituent is already registered for an event. They submit a second transaction where they are not registering themselves and are the payer/host for an unnamed guest. When the second transaction is processed through batch, the following exception may be returned: 

The selected constituent has already been registered in this event.
We are currently evaluating this issue and will update this article when we have more information.

Steps to Duplicate

1. Create a free or paid event form in BBIS that proceeds through a payment part. (Used event classic form in testing).
2. Submit a transaction with the following guidelines:
-Select 2 tickets for the event.
-Register two constituents that exist in the database.
Ex. John Doe and Jane Doe, John Doe is the payer
3. Process the transaction in batch - be sure that each registrant is matched to the existing constituent record.
4. Submit a second transaction in BBIS with the following guidelines:
-Select one ticket and add a guest that does not exist in the database.
Ex. Tom Doe
-On the payment screen, enter Jane Doe as the host/payer
5. In batch, link Jane Doe to her existing constituent record and mark Tom Doe as a unnamed guest.
6. Commit the batch and note the exception.

Was this article helpful?