A BBIS profile update batch comes through with the same constituent information that was just committed

You may see a situation where a BBIS profile update batch is downloaded into CRM and the some constituents appear in this batch that were just committed in a previous batch. 
This is due to how CRM processes the information.  If a profile update is completed on your website and the batch is pulled in, if a constituent makes another profile change (or doesn't think the change is complete and attempts to make it again) CRM will hold the change in a "pending" state until the first batch is committed.  As soon as that batch is committed the next download will process the next change that the constituent made towards their profile. 

Environment

 Blackbaud CRM
 4.0.158.0

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.