UNmerging records

Hi all -

We've run into an icky situation here in which someone in the Box Office scheduled a merge for a number of institutional records which should not have been merged.  I need to know if there is a way of UNdoing this.

Any advice that other organizations have in terms of safeguards that they have put in place to prevent merges that shouldn't happen would also be appreciated.

Thanks!

 

-Lisa

Parents
  • In terms of unmerging there's not an elegant way to do that.  I think a help ticket might be your best bet.

    For the future, there are several options you can use to protect certain records against accidental merge.  There is a Void Merge attribute which, if put on accounts, will keep them from being merged.  We also developed a corresponding CSI which we ask people to add to any records they mark with this attribute explaining why the record shouldn't be merged.  We've also put some rules in place so that only certain departments can merge certain accounts.  For example Development wants to manage all Corporate records or Membership wants to manage all merges where both accounts have a membership constituency.  We use CSI's to alert other departments if users identify potential dupes that they don't have the rights to merge.

    We put a lot of though into our merge process so if you have more questions don't hesitate to ask!  Best of luck getting your records untangled.

  • I have put together a string of queries for unmerging (had to use it twice so far) which I would be happy to share, with the proviso that you attempt this in Test first.

     

    There was a helpdesk solution out there, I think, that I used the first time I did an unmerge, so that’s probably a good place to start.

     

    As to the Void Merge attribute, there are companies out there that schedule jobs to add this to all accounts with certain values. Both customer type and constituency would work as a trigger for the application of this attribute.

     

    Lucie

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Kjersten Schladetzky
    Sent: Friday, February 05, 2010 12:11 PM
    To: Lucie Spieler
    Subject: Re: [Tessitura Technical Forum] UNmerging records

     

    In terms of unmerging there's not an elegant way to do that.  I think a help ticket might be your best bet.

    For the future, there are several options you can use to protect certain records against accidental merge.  There is a Void Merge attribute which, if put on accounts, will keep them from being merged.  We also developed a corresponding CSI which we ask people to add to any records they mark with this attribute explaining why the record shouldn't be merged.  We've also put some rules in place so that only certain departments can merge certain accounts.  For example Development wants to manage all Corporate records or Membership wants to manage all merges where both accounts have a membership constituency.  We use CSI's to alert other departments if users identify potential dupes that they don't have the rights to merge.

    We put a lot of though into our merge process so if you have more questions don't hesitate to ask!  Best of luck getting your records untangled.

    From: Lisa McColgan <bounce-lisamccolgan5409@tessituranetwork.com>
    Sent: 2/5/2010 10:58:59 AM

    Hi all -

    We've run into an icky situation here in which someone in the Box Office scheduled a merge for a number of institutional records which should not have been merged.  I need to know if there is a way of UNdoing this.

    Any advice that other organizations have in terms of safeguards that they have put in place to prevent merges that shouldn't happen would also be appreciated.

    Thanks!

     

    -Lisa




    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!

Reply
  • I have put together a string of queries for unmerging (had to use it twice so far) which I would be happy to share, with the proviso that you attempt this in Test first.

     

    There was a helpdesk solution out there, I think, that I used the first time I did an unmerge, so that’s probably a good place to start.

     

    As to the Void Merge attribute, there are companies out there that schedule jobs to add this to all accounts with certain values. Both customer type and constituency would work as a trigger for the application of this attribute.

     

    Lucie

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Kjersten Schladetzky
    Sent: Friday, February 05, 2010 12:11 PM
    To: Lucie Spieler
    Subject: Re: [Tessitura Technical Forum] UNmerging records

     

    In terms of unmerging there's not an elegant way to do that.  I think a help ticket might be your best bet.

    For the future, there are several options you can use to protect certain records against accidental merge.  There is a Void Merge attribute which, if put on accounts, will keep them from being merged.  We also developed a corresponding CSI which we ask people to add to any records they mark with this attribute explaining why the record shouldn't be merged.  We've also put some rules in place so that only certain departments can merge certain accounts.  For example Development wants to manage all Corporate records or Membership wants to manage all merges where both accounts have a membership constituency.  We use CSI's to alert other departments if users identify potential dupes that they don't have the rights to merge.

    We put a lot of though into our merge process so if you have more questions don't hesitate to ask!  Best of luck getting your records untangled.

    From: Lisa McColgan <bounce-lisamccolgan5409@tessituranetwork.com>
    Sent: 2/5/2010 10:58:59 AM

    Hi all -

    We've run into an icky situation here in which someone in the Box Office scheduled a merge for a number of institutional records which should not have been merged.  I need to know if there is a way of UNdoing this.

    Any advice that other organizations have in terms of safeguards that they have put in place to prevent merges that shouldn't happen would also be appreciated.

    Thanks!

     

    -Lisa




    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!

Children
  • Former Member
    Former Member $organization in reply to Lucie Spieler

    Open a help ticket.  The Tessitura consulting team wrote some code for us to do some unmerges.

     

    Also LP_VALIDATE_CUST_MERGE is your best friend.  I’ve added code to ours to make sure we’re only merging the same customer types (so someone can’t merge an individual into a foundation, etc), that there are no soft credits between the two accounts (that creates a mess!), and things like that.  I’d be happy to share the code if you are interested.

     

     -steve carlock

    Santa Barbara Center for the Performing Arts/The Granada

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Lucie Spieler
    Sent: Friday, February 05, 2010 9:21 AM
    To: Steve Carlock
    Subject: RE: [Tessitura Technical Forum] UNmerging records

     

    I have put together a string of queries for unmerging (had to use it twice so far) which I would be happy to share, with the proviso that you attempt this in Test first.

     

    There was a helpdesk solution out there, I think, that I used the first time I did an unmerge, so that’s probably a good place to start.

     

    As to the Void Merge attribute, there are companies out there that schedule jobs to add this to all accounts with certain values. Both customer type and constituency would work as a trigger for the application of this attribute.

     

    Lucie

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Kjersten Schladetzky
    Sent: Friday, February 05, 2010 12:11 PM
    To: Lucie Spieler
    Subject: Re: [Tessitura Technical Forum] UNmerging records

     

    In terms of unmerging there's not an elegant way to do that.  I think a help ticket might be your best bet.

    For the future, there are several options you can use to protect certain records against accidental merge.  There is a Void Merge attribute which, if put on accounts, will keep them from being merged.  We also developed a corresponding CSI which we ask people to add to any records they mark with this attribute explaining why the record shouldn't be merged.  We've also put some rules in place so that only certain departments can merge certain accounts.  For example Development wants to manage all Corporate records or Membership wants to manage all merges where both accounts have a membership constituency.  We use CSI's to alert other departments if users identify potential dupes that they don't have the rights to merge.

    We put a lot of though into our merge process so if you have more questions don't hesitate to ask!  Best of luck getting your records untangled.

    From: Lisa McColgan <bounce-lisamccolgan5409@tessituranetwork.com>
    Sent: 2/5/2010 10:58:59 AM

    Hi all -

    We've run into an icky situation here in which someone in the Box Office scheduled a merge for a number of institutional records which should not have been merged.  I need to know if there is a way of UNdoing this.

    Any advice that other organizations have in terms of safeguards that they have put in place to prevent merges that shouldn't happen would also be appreciated.

    Thanks!

     

    -Lisa




    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!

  • Former Member
    Former Member $organization in reply to Former Member

    Quick update - I have posted the code we use for unmerges to my files section here.  It's called lp_unmerge_customer-2.sql.  We have been using it to clean up some issues here with no problems so far, but please try it in Test before you use it in Live to make sure it does what you expect.

     -steve carlock

    Santa Barbara Center for the Performing Arts/The Granada