Just wondering if those sites that have been up on v.11 have developed some rules/guidelines for when to use Convert to Household vs Move Transaction.
I mainly see the Convert to Household being used when there is more than just Transaction that need to moved such as events, activities, and salutations as well as Affiliations/Associations.
Move Transactions is used when only transactions and related records are involved.
Thanks
We were looking at that – it is just matter of looking at the 2 folks and picking the one to convert Household. Both records could have transactions to move so why pick one record over the other – my thought was it would because of all the other info not related to transactions.
Would the result be any different if you just added the two individual records to a Household and for both did Move Transactions?
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Lucie SpielerSent: Wednesday, November 28, 2012 12:47 PMTo: McKinley, LeslieSubject: RE: [Tessitura Next Generation Forum] Convert to Household/Move Transactions
Convert to Household is what you use when you have an individual, and you find out that there is another individual who belongs with him/her in the same household. You take the first individual and use Convert to Household (which moves the information from that individual into the household record, then creates an affiliated A1 individual who has the same name as the original person). If you then take a second individual who already exists in the system, and add that patron as the A2, you might need to use Move Transactions for the A2 individual so that all transactions go to the household. That’s what we’re doing, anyway.
Lucie
_____________________________Lucie SpielerIT Development and Training Manager
Editor, Season Program BookFLORIDA GRAND opera
You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!
So I'll weigh in here - we don't have any fully written standards yet, but the thing to look at/think about is if any of the individual accounts have non-transactional information on them. You'll want to look at tabs like: Constituencies, Relationships, Research, Attributes, History, Connections, and Custom. Any information on these tabs will *not* move with the Move Transactions functionality.
So when you are looking at accounts you have to make a judgement call about whether that particular account has information that is best left on the individual or if it can be 'household' owned information. How much information is on the current individual account? If they are a basic account with just transaction info then it won't matter much if you do a convert to household or create a new household account and move the transactions up to it.
Where you run into trouble is when you have accounts with a lot of non-transaction historical information - then you have to ask yourself where should that information live? Is it stuff that is directly related to the individual (like a school or employment affiliation) or is it information you'd be happy to live on the household like a customer service CSI?
I've often found that the information is split - some wants to live on the individual and some on the household. This requires me to do some back-end canoodling unfortunately. (Shhh) In my ideal pony world we could move information around from any tab similar to the email moving functionality. (She says as she hides from the Tessi developers)
So that's my 2 (or more) cents.
Heather