I have the following situation I am trying to find a solution to:
I have an org record that had contribution history and memberships for the past few years. A member of this organization went online and renewed their contribution/membership, but did so by donating online and created a new account (the org record did not have an email address or login associated with it).
I would like to merge the two records but I know that our merge potential duplicate function will fail as the Delete ID has a constituency on it that will prevent a merge. The constituency is auto applied by the system due to the donation, so I can't manually remove it (System just adds it again).
My work around for this with individuals is to make a household out of the Keep record, add the delete record to the household, move all orders over to the household level, then I am able to delete the constituency from the Delete record (as the contribution is now on the household vs individual record). I am then able to merge the delete record into the keep record.
But with Organization records, I don't see a way to replicate that.
Before I go to further extremes (i'm thinking changing the record type from Org to Individual, doing my previous work around, then trying to change the new household account, back to individual, then to org?) is there any other potential ideas for merging these two records?
Thanks!
Jeff
I assume the constituency code is being added using a scheduled utility or job? Can you temporarily pause it until your desired merge is done? Or play chicken with the time, by removing the code from the Delete account, scheduling the merge, and manually running the merge procedure before the next time the constituency code is added?
I had Jeff post this as I tried to research it: but this is mostly an own goal on our side:
So what I need to figure out is a way to accomplish our goal (preventing accidentally deleting customers with important information) and allowing a work-around when we have confirmed that we want to do that. Ideally whatever override (maybe an attribute that the pre-merge check looks for) would only be available for box office managers.
You can completely customize the criteria for merging and prohibiting merging. Just edit LP_VALIDATE_CUST_MERGE.
Gotcha. I'm sure you've already gotten to this conclusion but it sounds like you could edit your LP_VALIDATE_CUST_MERGE like Brian mentioned so a patron who has the ranking and NOT the attribute is blocked, but if they have both they are allowed through.