Hello!
I'm extracting constituents to a file, using Extraction Manager, and want the primary salutation regardless of its type (or the salutation on the affiliate record for segments using Advanced Relationship Options). Is there a way to bypass the Salutation Type requirement under Data Selection. A "(none)" option, like in the Memb Organization dropdown, would be great.
Thanks!
Emilie
I don't know if this answer the question, according to the help doc: Salutation Type – This parameter determines the salutations selected for output. If a constituent has a salutation of the selected type that salutation is used, otherwise the primary salutation is used.
That field allows you to selected a higher priority salutation, so say a Board Salutation over any other salutation on the record. If the record doesn't have that sal type then it will default to the primary on the record whether that's the default or not.
Hi Melissa!
We don't have a priority ranking for salutations (like in the Board example) -- just whatever salutation happens to be flagged primary. The salutations used for affiliate records in Advanced Relationship Options do have their own salutation type. Unfortunately they're only a fraction of the segments and I wouldn't want that salutation prioritized for people who qualify through other criteria.
The salutations actually default perfectly in List Manager, but the ability to use Extraction Manager in a single go would really streamline things.
Hi Emilie,
Since there isn't a (none) option, the best workaround for getting the primary salutation for everyone regardless of type would be to add a new salutation type that isn't used for any actual salutations and then select that type when extracting. The result would be that anyone without a salutation of that type (which would be everyone) would return their primary affiliation instead. You could even inactivate this fake salutation type so that no one can select it for new salutations, though it would still be available for selection when running an extraction. I've passed on the suggestion for adding a (none) or (primary) option to our Product team, so hopefully at some point in the future this workaround won't be needed.
-Kevin
This sounds promising, especially if we can deactivate the dummy type. Thanks!