Hi all
I'm working with a database that has been created from extracts from a number of sources. This has resulted in multiple records (ie, more than just duplicate) for some individuals. So my question is, how do I merge these multiple entries into one?
Do I schedule several merge lines which all have the same Keep constituent but different delete constituents? Will this work in the same merge process or would I have to do it over several cycles?
How have you guys solved this problem?
Blair
Chris –
Have you customized your LP_ MERGE_CUSTOMER procedure? I’m using out-of-the-box v12.1 code and have just checked this against the vanilla AP_MERGE_CUSTOMER procedure. As of April 2013, that procedure uses last_update_dt in the constituent record to determine whether activity has occurred on a constituent since the merge was scheduled. Unless you have local code overriding that, serial merges into the same target in the same run of AP_ MERGE_CUSTOMER will fail (per a test this afternoon) because the first merge updates the last_updated_dt on the keep account.
Unknown said: [...] that procedure uses last_update_dt in the constituent record to determine whether activity has occurred on a constituent since the merge was scheduled. Unless you have local code overriding that, serial merges into the same target in the same run of AP_ MERGE_CUSTOMER will fail (per a test this afternoon) because the first merge updates the last_updated_dt on the keep account.
Ah, I see. We do ignore that check, though I didn't realize that that would have prevented multiple merges to one keep record (though that would have been annoying enough). We simply commented out the code that fails a merge with "Merge aborted! Reason: Customer activity took place..." long ago, after realizing that none of the (many) merges that had failed in that way had been modified in a way that would have caused us to not merge them, instead simply creating the unwanted extra step of scheduling the merge again. No regrets years later, and serial merges have been working splendidly as long as I can remember.
Thanks to both of you, We'll make sure the scheduled Merge Process includes this customisation for smooth sailing.