We've decided we want certain constituent information living on the HH where one exists, and we have hundreds of such individuals who have information that needs to be moved. I don't see any out-of-the-box ways to do this based on a list. Has anyone built a procedure to handle moving transactions in bulk?
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:
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.
Thanks so much for the info!