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.