Hello all,
The inevitable has happened (I’m actually surprised that it’s taken 6 years for it to happen): someone merged two records that shouldn’t have been.
I was wondering if anyone had a set of best practices or at least some recommendations on how to proceed with un-merging the two records.
Thanks in advance,
Rey
--
A. Rey Pamatmat
Tessitura Manager
The Public Theater
425 Lafayette Street
New York, NY 10003
(212) 539-8739
rpamatmat@publictheater.org
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,
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Steve Carlock Sent: Monday, January 10, 2011 5:45 PM To: Rey Pamatmat Subject: RE: [Tessitura Technical Forum] Customers Mistakenly Merged
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).
-steve
Information Technology Manager
The Granada
(805) 899-3000 x 111 (phone)
(805) 899-3081 (fax)
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of A. Rey Pamatmat Sent: Monday, January 10, 2011 2:20 PM To: Steve Carlock Subject: [Tessitura Technical Forum] Customers Mistakenly Merged
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!