Constituent Update rules should consider capitalization changes as a difference to a constituent names that could trigger review depending on how your update rules are configured.
Currently the Constituent Updates functionality (within Global Data Entry Settings) does not take into consideration case sensitivity, so this does not trigger a manual review as it does not see capitalization as different. (Constituent Update rules are used in constituent update batches and enhanced revenue batches)
Names are being updated to incorrect capitalization because these changes are not correctly identified as differences. This is particularly an issue with BBIS batches since we relay on the donor to type in their name with the correct capitalization and that does not always happen. Donor names are then updated incorrectly without warning to the batch processor.
-
Cassidy Eaton
- Mar 1 2016
| Organization Name (Please enter full organization name) | University of Michigan |
| Reported Version | 4.0 |
Related ideas
Ideally, this would be addresses on the web side of things, where the webpage can correct the capitalization prior to submitting to batch. Kind of like ensuring auto capitalization, like the settings in CRM, works on the web page. The one size fits all for this setting in CRM creates too many problems with other data in CRM.