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
You can’t have a household that doesn’t have at least one individual member.
If you have a man and woman married to each other and sharing the same last name, with standard Mr./Mrs. prefixes, it is better to make Mr. the A1 so that household salutations get created properly.
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
_____________________________Lucie SpielerIT Development and Training Manager
Editor, Season Program BookFLORIDA GRAND opera
Unknown said: 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.
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
where name_ind in (-1,-2)
and cust_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
Hi Heather,
We just went live on v11 today. I copied your SQL query and setup a list. Do you find a high number of accounts on a regular basis where ticket history needs to be moved to the household? I'm just wondering how prevalent of an issue we can expect this to be.
Thanks,
Chuck
Charles,
We went through the same thing when we converted to V11. From our experience, once you get things cleaned up initially, you shouldn't see that many records on an ongoing basis. We also have a custom report running to check for this situation (Individuals affiliated to a household who still have some kind of transactional history on their record) but the only time someone new pops up is if an existing individual with history is affiliated to a household and someone missed the step of moving transactions. Since that circumstance is against our business rules we want to know about it quickly. But the actual number of records after initial cleanup has been pretty low.
Hi Levi,
Thank you for the feedback. We are also adding this as a business rule in merges but it will be helpful to keep a watch for accounts that slip through the process (hopefully not many).
Hey Chuck -
The biggest place we see this issue is when merging accounts. I'm working on adding something to my custom merge tab, but haven't finished it yet.
For normal day-to-day stuff we rarely see them. As Levi says, it is only if someone forgets and that is few and far between. We run the list once a week to check and usually it is blank.
HTH,
Heather
Unknown said: [...] my custom merge tab, [...]
[...] my custom merge tab, [...]
You have a custom merge tab? As person that works on and thinks about merges a lot, this sounds interesting to me. Please describe, and - sorry if you did that at some point and I missed it!
Erg. Sorry, mis-typed. Should have said customized merge procedure. Nothing special - just tweaks and twonks related to our business practices trying to make our merged accounts needing as little actual manual massaging/cleanup as possible.
Didn't mean to get your hopes up!
Unknown said: Didn't mean to get your hopes up!
No problem, I was just intrigued by the possibilities: a custom tab for merges. What does it do? I wanna see it! :-)