Constituent matching still occurs even when configured to skip matching in imports

When importing an enhanced revenue batch and the template is set to ignore matching, records are still matched to existing constituents in the created batch.
We’re currently evaluating this issue for a fix in a future service pack. 

Steps to Duplicate

1. Log in to BBCRM.
2. Go to the Administration functional area.
3. Go to Imports.
4. Select an enhanced revenue import. 
5. Map the fields Name, date, Amount, the Address collection fields with in the New/constituent and the constituent field.
6. On the matching section of the import choose to ignore matching.
7. Run the import.
8. Open the batch and note some constituents matched.


 Blackbaud CRM

Was this article helpful?