The solution is so obvious, I can't see it!
We have a user group who, when creating a new constituent record, can modify the constituent's last name before the record is saved. This is super useful when searching on a last name to avoid duplicates, and omitting some of the last letters. For example, we could search on "tchaik." If it doesn't produce a match, then we go straight to new constituent and finish spelling the last name in the new record.
All other user groups cannot amend the last name until the new constituent is saved, or, they are forced to start the search over with the full spelling of the last name (the first name and middle initial can still be amended). This adds two extra steps and with difficult-to-spell last names, increases the chance for error.
I can't find the security object that controls this. I wondered if it's part of Preferences. Any ideas?
Thank you! Sue
Hi Sue
It's a setting in T_Defaults, Allow_Lname_Edit
Thanks
Ruth
I'm curious about this setting....is there a benefit to leaving it set to "No"?
Hi Jennifer - my assumption has always been that it's to force you to better search by last name before creating a new record (to avoid duplicates). In other words, if I spell the name Johnson and come up with nothing, then I go to create the new record and realize I mis-spelled it and change it to Johnston, then I didn't really search by the correct last name and should start over on the search screen.
That was always my best guess anyway.
Courtney is very correct. Exhaust ALL searches before adding a new one. Ask the right questions. Have you purchased tickets with us before? Have you ever been here? Whatever your protocol is. Trust me, avoiding duplicates is tough, but worth it. Take the extra 60 seconds and ask the correct questions and search as many ways as you can. I update my database every Friday and I have a file over 1" thick that I inherited of duplicates.
That makes sense. Thanks!