Customers Mistakenly Merged

Here’s what I found when I had to do this (copied from my “Oops” documentation):

A pair of constituents was merged in error. Is there a way to un-merge them?

There is not a mechanism in Tessitura to reverse the effects of a merge. Below are some suggestions that may be helpful in guiding you to manually separating these customers.

To un-merge the customer record:

·    Locate the T_ADDRESS row that was changed from the deleted customer_no to the kept customer_no and change it back to the original customer_no.

·    Locate the TX_CUST_SAL row that was changed from the deleted customer_no to the kept customer_no and change it back to the original customer_no.

·    Once the T_ADDRESS and TX_CUST_SAL rows have been reinstated for the customer_no of the customer deleted in error, the T_CUSTOMER record for the delete ID can be changed to re-activate it. To do so, you would change the INACTIVE column from its current value of 5 (signifying 'merged') to a 1 (signifying active) and the INACTIVE_REASON column should be changed to a NULL value.

Here are some things that you would need to do to unmerge ticketing orders:

·    Any orders, especially subscription orders, which can be determined to belong to the customer deleted in error can be changed to the correct customer_no by calling up the order(s) within Tessitura and changing the constituent ID for the order(s). The system will warn you that you are changing the owner of the orders, which you can accept.

·    When the order(s) you can identify have been reinstated, if the season to which they belong is still being processed by the LP_UPDATE_SUBS_HIST and LP_UPDATE_TKT_HIST procedures, they should be tied to the correct customer with the next run of the procedures. If these procedures no longer run for the seasons involved, the ticket/subscription history records will need to be manually changed to the correct customer_no.

·    In the record of the kept customer, locate the 'Merged ID' attribute (which references the delete ID in the Attribute Value) column and delete it. For example:
delete tx_cust_keyword where keyword_no = 6 and customer_no = 322694 and key_value = 1027132

·    Other data that may belong to the customer merged in error must be separated manually. Your best resource is your Test Server. If the test server is kept up-to-date, then the deleted customer’s information can be reviewed there to determine any manual updates required on the Live Server.

·    A Word document which lists all of the tables where customer data is merged which may need to be reviewed to determine what data needs to be manually updated will be posted on AIM along with the other materials from this IWT session.

[Bob Bell, VP Support and Network Services, Tessitura Network, Inc., March 22, 2006, Frequently Asked Support Questions Interactive Web Training PowerPoint]

Lucie

___________________________________

Lucie Spieler

IT Development and Training Manager

Editor, Season Program

Florida Grand Opera

8390 NW 25th Street

Miami, FL 33122

305.854.1643 x 1521

Box Office: 800.741.1010

To Give a Gift: 305.403.3315

www.FGO.org

2010-2011 | 70TH SEASON | THE MYSTERIES OF LOVE

Turandot | The Tales of Hoffmann | Don Giovanni | Cyrano

Rey,

I have uploaded to my files a stored procedure that MAY help with this.  It’s called lp_unmerge_customer-2.sql.

Obviously, try this in test first.  Let me know if you use it and if it works for you (I didn’t write it).

I did try it in Test and couldn’t get it to work. However, I was looking at what Lucie sent, and I think I can do it that easily. Luckily an individual constituent (recent single ticket buyer) was merged into a Foundation record, so it’s relatively easy to identify what belongs to whom.

Thanks everyone,

Rey