Home› Welcome to the FamilySearch Community!› Suggest an Idea

New Merge not working

LegacyUser
LegacyUser ✭✭✭✭
April 9, 2020 edited September 28, 2020 in Suggest an Idea
Chas Howell said: I have tried several times to merge Azro Scott Cory GQH1-3M3 into 9FS3-Z93 but nothing happens after entering a reason statement and pressing "Finish Merge". I was able to do a different merge earlier. Maybe someone could try the merge on PID 9FS3-Z93? Chrome Win7
Tagged:
  • New
  • Other
0

Comments

  • LegacyUser
    LegacyUser ✭✭✭✭
    April 8, 2020
    Jeff Wiseman said: I cannot either (masOS Sierra and Safari 12.1.2)

    Doesn't anyone ever test this stuff? You would think that the total inability to perform a merge using the new merge process would have been pretty obvious...
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 8, 2020
    Lyle Toronto said: Do you mean GQH1-3M2?
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 8, 2020
    Jeff Wiseman said: Yea, he did. If you go to 9FS3-Z93 then the PID GQH1-3M2 is shown as the potential duplicate. But if you try to merge them, you get Chas' results of the Finish Merge button just flashing but not doing anything.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 8, 2020
    Jeff Wiseman said: Not sure if this has anything to do with it, but on the "Step 2 of 3: Select the information you want to save" page of the merge, the new process has not created and "Unnamed Spouse" for the 2 duplicate children (with dissimilar PIDs) when you bring them over. This may be part of the reason that this particular merge is having an issue completing when some other merges will actually succeed.

    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 8, 2020
    Chas Howell said: Actually I tried the merge without bring over the duplicate children and it would still not merge.
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 8, 2020
    Chas Howell said: Right Lyle, sorry for the miss typed PID
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 8, 2020
    Jeff Wiseman said: Hmm. Well, as an engineer, I had to guess :-)

    However, the old merge process did this correctly and uniformly by inserting the proper placeholder for an unnamed spouse. You can probably check this out as it appears that they have just pulled the new merge software off the servers!
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 9, 2020
    Brett said: Jeff

    I am so please that I missed all the 'kerfuffle' with the NEW "Merge"/"Combine" process, due the time difference in my 'neck of the woods'.

    Waking up to ALL those Posts on the problems/issues with the NEW "Merge"/"Combine" process was frightening, to say the least.

    As usual, "NO Warning", released "In-Line" (or, at least, "Activated" later) ...

    A 'heads-up' "Banner" to the effect that such a 'Significant' "Change" was about to be implemented would not have done astray ...

    Again, obviously, "Testing"; plus, "Sign Off", by dedicated 'Worldwide' User/Patron "Focus Groups" is still NONEXISTENT.

    Brett

    .
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 9, 2020
    Jeff Wiseman said: Don't worry, once it is actually corrected and made to "work" (i.e., you can actually merge persons with it), it will be sprung on us again and you'll get to participate then :-)
    0
  • LegacyUser
    LegacyUser ✭✭✭✭
    April 9, 2020
    Brett said: Jeff

    I am not worrying ...
    I am not in any hurry for that NEW "Merge"/"Combine" process.
    I am so just glad I missed all the 'kerfuffle'.

    'Yes' ... I am sure it will be 'sprung on us again' ... instead of being, "Tested"; plus, "Sign Off", by dedicated 'Worldwide' User/Patron "Focus Groups" ...

    Brett

    .
    0
Clear
No Groups Found

Categories

  • 30.2K All Categories
  • 24.3K FamilySearch Help
  • 127 Get Involved
  • 2.7K General Questions
  • 443 FamilySearch Center
  • 464 FamilySearch Account
  • 4.5K Family Tree
  • 3.4K Search
  • 4.7K Indexing
  • 639 Memories
  • 6.6K Temple
  • 326 Other Languages
  • 34 Community News
  • 6.6K Suggest an Idea
  • Groups