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
Our AppSupport will bless you – cause this is exactly what I had on my list for them to create.
Thanks so much Heather
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Heather KraftSent: Thursday, November 29, 2012 8:43 PMTo: McKinley, LeslieSubject: RE: [Tessitura Next Generation Forum] Convert to Household/Move Transactions
I've been meaning to post this little bit of list SQL - and this thread seems like a good place. This is only useful if your business rules are to push all transactions to the household and you want to check to find people where this hasn't happened. (This could be the result of a merge or someone forgetting to move transactions to household when affiliating them to a household account)
I put this SQL in a list via manual edit - it looks for anyone who is in a household but has orders or contributions still on their account (it doesn't check for everything, but these are the big guns for us).
Then I scheduled the 'Generate a List' report which is mailed to my box office who goes through and checks the accounts and cleans them up. It helps keeps our data consistent so we don't have random orders on an A1 or A2 until we actually WANT them there in later Tessi versions.
Anywho - just in case it is useful to someone out there!
select distinct(ch.customer_no)
from
(SELECT distinct(customer_no) from V_CUSTOMER_WITH_PRIMARY_AFFILIATES
wherename_ind in (-1,-2)
andcust_type = 1 ) as ch
JOIN dbo.T_ORDER o on ch.customer_no = o.customer_no
UNION
JOIN dbo.T_CONTRIBUTION c on ch.customer_no = c.customer_no
From: Chris Jensen <bounce-chrisjensen8841@tessituranetwork.com>Sent: 11/28/2012 1:13:43 PM
Lucie Spieler:I wish that it was as easy to move constituencies, attributes, postal addresses, and other such information among members of a household the way you can move eaddresses…
Lucie Spieler:
I wish that it was as easy to move constituencies, attributes, postal addresses, and other such information among members of a household the way you can move eaddresses…
I agree: the "transfer owner" button would be very handy to have under all the radio buttons under Contact Details, as well as Attributes, Consts, Relationships; basically almost anywhere that the "group by constituent" functionality exists.
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!
Just to second what Heather was saying earlier - we've actually stopped "Converting to Household" because we have a lot of non-transactional data on individuals (attributes, interests, emails, etc etc). It is so easy to create a new household that making a household and filling it with people has not been an issue. If transferring details between affiliates was more readily available (and more than just eaddresses), we might change our tune. But for now, no "Convert to Household" allowed.
Another thing we've noticed with Move Transactions though is that history/activities and history/events do not move to the household, either. It hasn't negatively impacted us as of yet, but it might for some. Also had a little trouble initially with how our custom reports pull benevolent (donated) seats. They also continue to exist on the individual in the database table.
Also, like Heather, we have a dynamic list that pulls households that need transactions moved - though we did it without custom SQL. (Though the custom is more comprehensive, most likely).
Tickets - Season In (all seasons selected)Constituent Type In IndividualRelationship Type In Adult MemberORContribution Amount >= $1.00Constituent Type In IndividualRelationship Type In Adult Member
-------------Beth