Our Migration - Check Database report spat out quite a few customers with the following error:
"Address 742 Evergreen Terrace is linked to salutation type Head Honcho which will not end up on the same record. Will be unlinked."
Now, while originally going through the workbook with our migration team, we got to the section about salutations and when we answered NO to both questions asking about name specific salutation types, we thought we were through, as we do not have any [N1/N2-specific types].
It would seem the aforementioned errors are related to salutation types and our having not touched TRU_SALUTATION_MAPPING at all.
So, what are the implications of the above error and how do we separate the salutations? Do we actually have to create a duplicate set of salutations for name 2 and have some specially written procedure update the name2 records to the new Name 2 version of the salutations to make sure things map right?
Thanks, Tessiturians.
Hi Matt,
For salutations what is probably happening is that the 742 Evergreen Terrace has an address type which is mapped to the Name 1 or Name 2 account, and the Head Honcho salutation is staying on the household. When an address and salutation are linked the address is selected first, and the salutation selected will always be that salutation. If the link is broken then the salutation selected for the address will be salutation specified on the report or mailing.
So let's assume that the 742 Evergreen address is a Name 1 Business address. In Version 10 you would get the 742 Evergreen address and Mr. Plow salutation. In the migration the business address will move to Homer's account, and the salutation will remain, so in v11 you will get Mr. Homer Simpson at 742 Evergreen Terrace.
There is no requirement to resolve this, but if you did want to do data cleanup in preparation for v11 so the salutation follows the address, you would make a Name 2 Head Honcho salutation type and a Name 1 Head Honcho salutation type and update the addresses appropriately. If there are a lot of these at issue you can certainly script something like this to say, when the address is a Name 2 address type and the salutation is head honcho, update tx_cust_sal and t_address to use the Name 2 Head Honcho salutation. If it is just a handful then you can do the updates manually using the list.