Good morning -
We recently updated a student's first name on their constituent record. I changed it on the general tab, I created an alias for "former name", I double checked that the new/correct name is listed on the relationship tab, and I confirmed that the initiator and recipient on their academy tuition orders is appearing as the new/correct name. It appears correctly everywhere on the record, the only place where the old name appears is in the former name alias.
But I created a dashboard for student rosters, and it exported the student's old name. The criteria I used is "recipient sort name", and on the order in the record the recipient name is correct. So why is analytics returning the old name?
Any ideas?
Thanks all!
nuh uh....
Kanani Reichlin I blew my own mind when I figured it out! Ha! I was working on some custom SQL to get first names into a WordFly list for households and was working on Salutations when I found it in the documentation. It should definitely be mentioned during implementation!
I'm guessing it will change in V16 --generally no right-clicking on the web screens, but I hope it stays in some form.
The problem is that if a user has updated the salutation manually for some reason then that work will be blown away. Salutations are still poorly supported for a consortium. They've made some baby steps with allowing salutation types to choose a preferred salutation format, but utilities are still lacking.
That definitely is really cool. Our org uses control grouped salutations in our consortium.. I'm going to start right-clicking on everything while we still have 15 lol
Correct, Gawain Lavers. We make sure to put a special note which appears in the header on any account where there has been manual manipulation of the salutations. Absent that note, people know they can click the button.