Duplicate versions of constituent solicit codes are created when importing into Enhanced revenue batch or Constituent update batch

 When the 'Constituent Updates' import setting is set to require manual review for Name, address, email or phone, duplicate versions of a constituent's solicit code are created. 
Corrected in Service Pack 17 Hotfix 2.

Steps to Duplicate

Steps to duplicate:
1.  Add a new constituent with First name, Last name, Email address and a solicit code.
2.  Create an  Enhanced revenue batch or Constituent update batch import type and .csv file for the import using the constituent created in step #1.
3.  Automap fields and then make sure you map the "New/Edit constituent" collection fields with the Constituent field for Last\org\group\household name, the Email type and the Email address
4.  Under the "Set options" tab of the import "other" tab - check "Add new entries" for Code table fields, and use "Quick find" for Search list fields.
5.  Under the "Set options" tab of the import, set Constituent updates tab to un-check "use batch template settings" and set  "Require manual review (generate exception) for Email addresses.
6.  Save the import.
7.  Under Tasks click "Start process".
8.  Note that batch errors are generated. Navigate to the batch.
9.  There may be an import error reported "Multiple results for field "Constituent" using search list "Batch Revenue Constituent Search" were found, so an exact record could not be determined" - this can be ignored/dismissed.
10. Check the Solicit Code collection and see that the existing solicit code has loaded correctly.
11. Exception message "Data in batch is different from data for this constituent. Click here to review" is displayed - Click the hyperlink.
12. Click "Update existing" and select Update all email fields.
13. Save and close review screen,
14. Validate the batch.
15. Exception is generated: A constituent with the same solicit code must not have overlapping dates.
16. Check the Solicit Codes from the batch grid and see that duplicate solicit codes were created and causing the exception.


 Blackbaud CRM
 Service Pack 17 Hotfix 2

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.