Importing to a Constituent Update Batch does not display existing constituencies in batch and replaces all constituencies on the constituent record with the new constituency from batch

When a batch is created from a constituent update batch import process, the existing constituencies on the constituent record are not displayed in batch. This happens when a user is importing with LookupID, LastName, and Constituency. Instead, the new constituency in the import is added to the constituent record (removing all other constituencies).

Article
Number:62655

Products:

Blackbaud_CRM

To prevent the process from removing existing constituencies map the LookupID field in your import file to the Constituent field in your import process. This will pull in the correct constituent without running the de-duplication process that removes existing constituencies.

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.