Constituent not automatched from finder number in a BBIS Event Registration Transaction batch

After entering the finder number on a Payment 2.0 form, you might notice that an event registrant does not auto-match to an existing constituent record based on that criteria.
We are currently evaluating this issue for a fix in a future service pack. 

Steps to Duplicate

1) Create a marketing effort with an appeal.
2) Add a constituent segment and reserve finder numbers for the effort.
3) Calculate segments and activate the effort.
4) Create an event with the same appeal used in the marketing effort.
5) Go to a constituent record from the marketing effort segment and take note of the finder number assigned.
6) Create a BBIS Event Registration form (Classic) and add the newly created event to the form.
7) On the Payment page used in the form, make sure registrants can enter their finder number.
8) Register for the event using that finder number.
9) Download the transaction in the Web functional area of CRM.
10) Open the batch and notice that the finder number wasn't automatched to the constituent.


 Blackbaud Internet Solutions

Was this article helpful?