Do not update collection fields in constituent update batch if no field values have been changed
When loading a constituent with addresses/emails/phones in a constituent update batch row, the existing contact info records are defaulted into the corresponding CUB collection fields. When a user commits the CUB without changing any of the records in these collection fields, the DATECHANGED and CHANGEDBYID fields on these records are updated even though nothing else on the record has changed.
-
Heather Johnson
- Oct 26 2015
| Organization Name (Please enter full organization name) | The Ohio State University |
| Reported Version | 4.0 |
Related ideas
We are experiencing the same issue here at Brown and this really needs to be fixed. We are not actually making changes to those other addresses so it makes no sense as to why the batch would pull them in and then update them, causing a change date. This is making life very difficult for us as we use change dates in our reporting.
Attachments Open full size
Specific example: when committing a modeling and propensity update batch to add an attribute, the “Update On” date field that displays for each model score in Wealth & Ratings changes on the built-in Blackbaud scores (non-attribute fields), even though none of those fields were in the batch and built-in model scores weren’t updated.
Bequest Likelihood changes to the start date of the imported attribute.
All of the other scores (Annual Giving Likelihood, Annuity Likelihood, CRT Likelihood, Major Giving Likelihood, and Target Gift Range) change to reflect the date of the most recent modeling and propensity batch commit to the constituent’s record.
Attachments Open full size