Preference code not committing to constituent record after import

When a Preference code is imported and the batch from the import is committed, the Preference code is not committed to the constituent record.
Currently standard solicit codes do not have a preference, only Consent Solicit codes have these which is why this is working in the manner described which is as intended. 

Steps to Duplicate

1. Go to the Administration functional area and click Import.
2. Add a new import based on a Constituent Update Batch template. 
3. Create a CSV file to import with these fields populated:

Last/Org/Group/Household name
Solicit Code 1
Preference 1
Start date 1

3. Map the fields accordingly in the import.
4. Save and run the import.
5. Go to the batch created off of the import and commit it.
6. Go to the constituent's record.
7. Click the Communications tab followed by the Preferences tab.

Environment

 Blackbaud CRM
 4.0
 4.0.180

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.