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.
 

Environment

 Blackbaud CRM
 4.0
 4.0.173

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.