Merging patron accounts

You can enforce your own house rules for merging by defining them in [LP_VALIDATE_CUST_MERGE].

BWG

Since the address is inactive it will not be used.  Our practice is to keep the old address for reference and historical info. 

At Bass Hall - Fort Worth, we turned the "full time" Tessitura switch this past July.
Patrons from the legacy system now connect to Tessitura (through TNEW) and either update or create new accounts.  Not surprisingly, this activity generates many duplicates, and I search for duplicates on an almost daily basis.

When merging patron accounts, I usually select the newest account as the final account because the data is more current.
During the merge operation data from the "old" account is moved to the "new" account, including "old" addresses that now appear as inactive in the "new" account.
After the merge I must open the "new" account and delete the "old" and now inactive addresses (these addresses are usually duplicates of "new" addresses).

My question:
When merging accounts, is there a way to prevent "old" postal address records from moving to the "new" account?
Similarly, is there a way to prevent the "old" email address records from moving to the "new" account?

I use the stored procedure ap_merge_customer2. 
Is there a better process to merge customer records, or a more appropriate stored procedure?

Thank You
Wendell Baskin
Bass Hall - Fort Worth

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

You can enforce your own house rules for merging by defining them in [LP_VALIDATE_CUST_MERGE].

BWG

Since the address is inactive it will not be used.  Our practice is to keep the old address for reference and historical info. 

At Bass Hall - Fort Worth, we turned the "full time" Tessitura switch this past July.
Patrons from the legacy system now connect to Tessitura (through TNEW) and either update or create new accounts.  Not surprisingly, this activity generates many duplicates, and I search for duplicates on an almost daily basis.

When merging patron accounts, I usually select the newest account as the final account because the data is more current.
During the merge operation data from the "old" account is moved to the "new" account, including "old" addresses that now appear as inactive in the "new" account.
After the merge I must open the "new" account and delete the "old" and now inactive addresses (these addresses are usually duplicates of "new" addresses).

My question:
When merging accounts, is there a way to prevent "old" postal address records from moving to the "new" account?
Similarly, is there a way to prevent the "old" email address records from moving to the "new" account?

I use the stored procedure ap_merge_customer2. 
Is there a better process to merge customer records, or a more appropriate stored procedure?

Thank You
Wendell Baskin
Bass Hall - Fort Worth

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!