Hi, I am going nuts working with merges! We have had an influx of Individual Web records that I now need to merge with pre-existing Household Records.
I am trying to keep the New Individual Web record only becuase of the Web Login and merge it into the pre-existing Household record of which the Web Individual is an Affiliate.
How do I do this? I keep on getting errr messages like "cannot merge customers with two different customer group types" or "cannot merge customer with primary affiliation into one that has none"
I have tried converting the record I want to keep into household and adding the second household affiliate name but then I get the Household Merge Helper. Seems like too much work for something simple... Am I approaching it the wrong way though? Is there a way I can just save/transfer the Web Record's Online Login info?
Any suggestions would greatly help,
Thanks, George
George,
If you want to save a bit of time, you can simply convert the new individual record from the web into a household and merge the household of one person into the household with two people. You’ll still have to use the merge helper, but it would allow you to get all of the information (web login included) onto the correct account.
The only other way I can think is if you merge the two individuals and then move transactions to the household after the merge process has completed, though it would require you do take care of the process on two different days which doesn’t really shorten the process. Also, this would move the web login onto the individual account so it really depends on your org’s standard for where you keep your emails and login info.
Hope that helps!
Laine
---
Laine Kyllonen
Database Application Specialist
Science Museum of Minnesota
(651) 265-9870
"Tornado Alley will blow you away," said Pioneer Press movie critic Chris Hewitt about the new Omnitheater film. Audiences will ride along with storm chasers in the Tornado Intercept Vehicle (TIV) and experience "how thrilling it can be to chase after big storms." Make plans to see Tornado Alley in the Omnitheater, and see the TIV in the lobby of the Science Museum.
Reserve your tickets and watch the trailer at www.smm.org
From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of George SyrigosSent: Wednesday, January 09, 2013 9:35 AMTo: lkyllonen@smm.orgSubject: [Tessitura Development Forum] How do I merge as keep an individual record into part of a household record?
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development 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!
Laine's second suggestion is what we do at City Center; we merge the web-created records as Delete IDs to the corresponding Individual already attached to the household. We then move the web order to the Household and make sure that the web-created login and e-mail are primary in case they were inactivated because they were on the Delete ID.
Our scheduled merges go through every two minutes, though, so we don't have the delay between scheduling a merge and editing the record.
I was pleasantly surprised to learn that our donors can log in with a login that exists on their Individual record and their resulting web ticket order ends up on their Household record.
And we do what Michael does here at UMS - merge the two individuals. Our merges are scheduled to process overnight, so we don't necessarily get to moving transactions right away - but we have a dynamic list that keeps an eye on accounts that have transactions that need to move to the household, and that gets cleaned up frequently enough.
One thing though I've noticed when merging is that an active weblogin (and the email it is attached to) on a Delete ID will *not* become inactive when the accounts are merged - unlike postal addresses and other emails. So often, to save time and cleanup, I'll make the newer web created account the Delete ID, and get rid of extra postal or other address information (making sure it is updated in the Keep ID first!). That way they keep the weblogin info, and we have less to go back for after the merge. (We have the T_DEFAULTS setting that allows for any primary contact info, and does not require a postal address).
Beth
BETH GILLILANDUMS Tessitura System Administratorbethgill@umich.eduwww.ums.org // www.umslobby.org
Like some others above, we also would merge the new individual record into the existing affiliate individual, then optionally move trns, and/or logins, etc, to the household the next day (some we want to leave as is, particularly education).
All of our merges are checked for various things, by human eyes, the next day.