Constituent Update Batch Import does not update primary address flag properly if address already exists

When importing existing addresses in a Constituent Update Batch to change the primary address flag, you might notice that the changes do not appear in batch.
We are currently evaluating this issue for a fix in a future service pack.

Steps to Duplicate

1) Create a constituent and add 2 addresses with different types.
2) Set Address A to the primary address.
3) Create a constituent update batch import process and import the two existing addresses with all the same information except setting Address B to the primary address. (Address A - Is Primary - FALSE; Address B - Is Primary - TRUE)
4) Run the import process and notice that the batch does not have the changes present.

Environment

 Blackbaud CRM
 4.0
 4.0.180.1600

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.