We recently went through Converting a Household and Moved Transactions and we noticed an issue. Many Constituencies are directly related to Monetary Transactions (Membership and Ticketing Constituencies). In those instances, when we move the transactions to the household the corresponding Constituencies are not going with them. There are additional constituencies that provide web access that need to be on the household. Has anyone come across this and what was the solution?
Also, has anyone leveraged LP_Customer_rank to move transactions/move constituencies without having to move them manually?
Constituencies can be triggered by so many things, I bet the Network won't roll that into moving transactions. We've always set up (nearly) all of our constituencies with the way the Membership Update sproc works in mind, i.e. custom code runs nightly that does things like: based on the existence of X, constituency Y is added or reactivated; if the constituent has Y but X is missing, deactivate Y.
So, constituencies set up this way move automagically from Ind -> Household if transactions, orders, or whatever, move that way.
If I were you, I would set something like this up, perhaps on a less than daily or even manual basis, as needed, if you didn't want to run it that often.