Hello Tess Community!
I'm hoping someone can provide a bit of guidance on this, as I'm sure this has to be 'operator error'; but after more than half a day of experimentation and testing, I'm still not finding the appropriate solution.
My organization currently uses 2 different salutations:
1) A Formal Salutation where esal_desc = fname + lname and lsal_desc = fname + lname. This is currently set as the default for our constituent types in TR_CUST_TYPE.
2) An Informal Salutation (Fundraising Department's preference) where esal_desc = fname + lname and lsal_desc = fname. (Added in manually to each account if a donation is received)
I would like to be able to go in and only update the informal salutation with the pre-defined informal salutation format which is already set up in TR_SALUTATION_FORMAT via the Rebuild Salutation utility. However, because the default salutation type in TR_CUST_TYPE (for all constituent types, in our case) is set to the formal salutation format, I end up the informal salutation with the formal salutation format. The only way I can seem to get the informal salutation to update with the correct format is by changing the default salutation type setting in TR_CUST_TYPE for each applicable constituent type.
It seems, to me, to defeat the purpose of being able to create additional formats, if you can't use them without changing your default settings...which is why I'm sure I must be overlooking something obvious.
If anyone can point me in the right direction, I would be most appreciative!
Thank you!
Mandy
I share your pain. What you've discovered is indeed how the system is architected.
The idea seems to be that only the default salutation type is ever autogenerated, and other salutation types (from TR_SIGNOR) can be manually added and edited. The notion of separate "casual" or "formal" salutations that are autogenerated by different TR_SALUTATION_FORMATs doesn't track with this. You can achieve the desired result with a lot of customization, but that's really it.
I believe there is a re-think of this planned for V16, but I don't know what the details are.