Merge Process Skipping Multiple Duplicates

Any merge failed messages showing up in the duplicate merge report or are they just not being considered at all?

Yes, thanks for reminding me.

The report outputs that there has been activity on the kept id since the merge was scheduled. Of course this is true, since it was just merged with another dupe. Is there some circular logic at work here?

Have you typed in the account number in question to ensure it didn't in fact merge?
I think I remember seeing this error but finding that the accounts merge anyways.
Also are you sure no one had made any manual changes after the merge was scheduled which I think returns a similar if not identical error.

Have you typed in the account number in question to ensure it didn't in fact merge?
I think I remember seeing this error but finding that the accounts merge anyways.
Also are you sure no one had made any manual changes after the merge was scheduled which I think returns a similar if not identical error.

I did double check and unfortunately there are still duplicates in the system. I also know that there were no changes to any of the accounts I'm testing, other than that they were merged.

Hmm, could it be something in lp_const_merge that is causing the second merge to fail? Sorry I couldn't be of more help.

Merging multiple accounts at the same time is working fine for me. I tested earlier today and just now to double check.
The kept account needs to be the same for each of the multiple merges I think, so maybe that is the issue.
Also could the merge fail if something in lp_const_merge is scheduled to happen pre-merge where @merge_stage = 'B' as opposed to after?

I found that if I enter in the keep/delete id numbers manually, then the procedure works for all scheduled merges. Ryan, were the merged you tested manually entered or were they scheduled via the Identify Dupes screen?

Thanks for all of your help!

Huh, that is very interesting. I did them manually.
I wonder why they fail otherwise...
I'll try the other way and post if it works for some reason.

Cheers!

So I could not merge multiple accounts when highlighting the accounts from the identify dupe screen either. It appears that when done manually there is a one-to-one entry in the kept and deleted id boxes, whereas when you highlight the accounts there is only one entry in the kept id box regardless of how many are associated in the delete id box. I wonder if that is the intended result or a bug.

As Matt pointed out, the merge process fails because the Kept ID has been updated as a result of the first merge. The documentation says that manually scheduling the merges will override that part of the code. So it's behaving normally, I guess. I had thought that the code would make an exception for records updated via the merge procedure, but apparently that's not the case!

ah ha, documentation to the rescue! Thanks for helping me learn something new.

Cheers!

ALTHOUGH, I notice that on page 9 of the documentation there is a screenshot of a merge queue that has two duplicate Delete IDs (James Freund, Jimmy Freund) for one Kept ID (Jim Freund). So it looks as though the process should work that way and maybe there is a bug. But at least there is a way to make it work, even if it's not ideal.

Thank YOU!

Hi,

Coming in on this conversation late in the piece sorry - I've been manually scheduling multiple duplicates and have come across an issue where some of them get left behind in the 'Kept ID' column on the merge screen. These seem to be accounts where there is a combination of household and individual merging happening. It allows me to schedule everything fine (all individual records into one individual record, and all household accounts into one household account).

The duplicate merge report isn't showing any failures, though they obviously are failing as only one individual and one household account successfully merge, and the rest get left behind. Short of running the merge_customer2 procedure after each manual scheduling, do you know of any work around for this? Or how to get rid of the list building up in the Kept ID column?

Many thanks in advance for any advice on this one!

Just a follow up to this - quite a few are actually merging successfully, just leaving a copy of the Keep ID (sometimes multiple copies) in the Kept ID column, so the list is growing! I can work around it by running the merge proceedure manually between each scheduling, but as soon as I line up several merges, the list grows again. Not a showstopper, but annoying!

Hi Emma -

The keep ID issue is a known one to Tessitura (I reported it on TASK a bit ago) and happens in conjunction with using the Household Helper in the merge screen as far as I can tell.

- Heather