Mass Move Transactions to Household

Chaz,

I have in fact done this exact thing.  I just have a nightly procedure that runs and moves all transactions to the Household.  Happy to share if you want to e-mail me, but it really is nothing much more than getting a list of relevant accounts and then putting that into a cursor which executes the standard "move transactions to household" procedure against every account on the list.  My e-mail is jmoskal@thecenterpresents.org if you want.

John

Hi John! I just wanted to ask what kinds of data entry situations lead you to need this running as a standard maintenance procedure. It feels uncommon to me but I would love to know how it happens in the real world. Thanks!

-Michael 

When accounts are modified manually.  Example:

• Patron A creates individual account and buys tickets to a performance.
• Patron B makes a donation; Development department creates an account and processes contribution.
• Development later discovers that Patron B is Patron A's spouse.
• Patron B's account is converted to a household and Patron A added as an affiliate.
• Patron A's ticket order needs to be moved to the household.

The merge procedure should take care of individual accounts that have transactions.  But with the situation above, there is no merge in process, so that never comes into play.

The Development, etc... involvement above is just one example, but that sort of thing comes up pretty regularly in terms of general account clean-up and maintenance for our database.  We are also a consortium environment, so there are routinely multiple departments and organizations making account changes, so to be able to depend on the procedure catching the transactions is much more satisfying for me than depending upon people to check and manually move them when they are making the account changes.

The Development, etc... involvement above is just one example, but that sort of thing comes up pretty regularly in terms of general account clean-up and maintenance for our database.  We are also a consortium environment, so there are routinely multiple departments and organizations making account changes, so to be able to depend on the procedure catching the transactions is much more satisfying for me than depending upon people to check and manually move them when they are making the account changes.

Thanks so much for the info!