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. 


 Blackbaud CRM

Was this article helpful?