Solicit codes system fields get updated on batch commit

Seeing the DATEADDED and DATECHANGED fields in the dbo.CONSTITUENTSOLICITCODE table update to the same time a Constituent Update Batch is committed even when the batch does not contain any updated solicit codes for the records being updated via batch.
dbo.CONSTITUENTSOLICITCODE DATEADDED and  DATECHANGED fields of a solicit code update when a Constituent Update Batch is committed.  This stems from the way CRM is handling data during the update.  Regardless of the specific solicit code, our developers found removing and re-adding all solicit codes was a better choice than attempting to update specific codes.  The side-effect of this is that the DATEADDED/DATECHANGED fields get a new timestamp.
 

Environment

 Blackbaud CRM

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.