Previous merging process was less complicated.

LegacyUser

Twila Edith Eyring said: Change to merging process is more complicated. Has glitch. Example: tried to keep ID KG45-QHP which had more info, however it would not merge. Was required to keep G3GY-9NM which had less info - had take time to move the info.
It should not matter which ID is used to keep & which to delete. It should work no matter which ID is used in the keep column or the delete column.

LegacyUser

Ali Jessee said: Hi Twila!

Thanks so much for reaching out. We've had a few other reports like this, so you're not alone! Thanks to your quick reporting, we're digging in to find out what the problem is and hope to have it resolved soon!

Thanks,
Ali

LegacyUser

Kristi Etherington said: Looks like you were able to get these merged.

LegacyUser

Jeff Wiseman said: Kristi, she solved the problem by reversing the merge and manually carrying the bulk of the data over into the more sparse duplicate. The problem still exists.

LegacyUser

Brooks Connor Gould said: I completely agree, I love all the changes that are being made around family search.. except the new merging duplicates. I hate the new process, its much more confusing and I think will create a lot of errors. The other system was much simplier and clearer. I dont like that information is automatically moved over (like spouse, or census location), the two people have switched sides (the left side used to be the original person), and looking at the sources you now have to create a new tab to see the information instead of it just popping up on the same screen like it used to. Please switch back to the old system.

LegacyUser

Tom Huber said: Once a change has been made with an update like this, FamilySearch seldom (if ever) backs out a change. Instead they work on getting the bugs out of the code as they are reported in this and by other means.

My own issues with updates go all the way back to when the Help Center and Learning Center were two different systems. They were combined into what I called the HelpLESS center where one had to guess at the keyword that would produce the desired results.

Since that time, FS has slowly modified and improved the Help Center. Today, it is still largely a guessing game, but it is easier to narrow down the results and get what I'm looking for.

LegacyUser

Jeff Wiseman said: It appears that they just backed out the new merge software. I guessing that they'll reinstall it after some further updates.

I preferred the older system but I understand what they are trying to do with this, so I have no qualms about it changing (other than the confusion it creates).

LegacyUser

Jeff Wiseman said: By the way, moving relations (i.e., spouses or children) across by default is actually a very good idea since it prevents family on TRUE duplicates from being split up and person records cut free and floating in the system. This has been requested several times. If you are merging people due to duplicates, there is always the possibility of relation duplicates as well. The easiest way to deal with that is to ALWAYS bring across ALL relations and then clean them up AFTERWARDS.

In fact, I have very rarely NOT brought some of those across. Not bringing them across is normally a rare exception