New strategy for new duplicates

We are still not certain what will happen as how mailings/messaging to the person is still being determined.   One thing we determined we wanted to do is put the person’s name in the Alias of the Corp/Fdn so the record could be found in v.11.    Depending upon the interaction with the Group some of our Dev folk are used to typing Name 2 to find the record not the company or foundation name and we don’t want to lose that.    It mirrors what is being done for Corporate Contacts.

We also are giving the Name 2 a specific affiliation under employment so we can easily identify the Name 2 record and work with it as needed.

There is no primary affiliate on a Group record as I understand it.   Affiliations can be ranked so they may appear in a particular order when a Group record is retrieved.

One of the first things we noticed in our v11 test is the new duplicate accounts created when there is a name 2 on an organization. Prior to v11 we called the "purposeful dups" - one person who was a primary contact for an organization might be the name 2 on the org account, but also have their own individual account. 

Has anyone developed a strategy for merging these new duplicates, or at least identifying them? We were considering taking the name 2s off account before we upgrade for any accounts where the name 2 is already an individual account. If there is no name 2 on an individual account, would an associated account become the primary affiliate in v11? I think that would be handled by tru_association_mapping. Is that correct?

You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

We are still not certain what will happen as how mailings/messaging to the person is still being determined.   One thing we determined we wanted to do is put the person’s name in the Alias of the Corp/Fdn so the record could be found in v.11.    Depending upon the interaction with the Group some of our Dev folk are used to typing Name 2 to find the record not the company or foundation name and we don’t want to lose that.    It mirrors what is being done for Corporate Contacts.

We also are giving the Name 2 a specific affiliation under employment so we can easily identify the Name 2 record and work with it as needed.

There is no primary affiliate on a Group record as I understand it.   Affiliations can be ranked so they may appear in a particular order when a Group record is retrieved.

One of the first things we noticed in our v11 test is the new duplicate accounts created when there is a name 2 on an organization. Prior to v11 we called the "purposeful dups" - one person who was a primary contact for an organization might be the name 2 on the org account, but also have their own individual account. 

Has anyone developed a strategy for merging these new duplicates, or at least identifying them? We were considering taking the name 2s off account before we upgrade for any accounts where the name 2 is already an individual account. If there is no name 2 on an individual account, would an associated account become the primary affiliate in v11? I think that would be handled by tru_association_mapping. Is that correct?

You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!