Home› Welcome to the FamilySearch Community!› FamilySearch Help› Family Tree

New Defect - Merge Reasons Are Mapping to Residence Reasons

Mark.B.Hansen
Mark.B.Hansen ✭
September 18, 2021 edited September 18, 2021 in Family Tree

Don't know if any system support people read these posts, but there is a new defect (or I just noticed it recently, last few days). Whenever I merge a duplicate, I am asked for the Reason for Merge. But once I enter the reason and complete the merge, the Reason for Merge automatically maps to the Other Information> Residence> Reason This Information Is Correct field. This is a defect and needs to be fixed. Attached is a screen shot (before I manually deleted it).

Example of FS Reason for Merge Mapping Error.jpg


Tagged:
  • Help & Feedback
  • merge problem
0

Best Answer

  • CHold
    CHold mod
    September 18, 2021 Answer ✓

    @Mark.B.Hansen

    Thank you for reporting this. The engineers became aware of this on Wednesday of this week and they are working on this bug. Please be patient as they work to resolve this. We are not sure on the time frame so maybe check back in a week or so.

    We appreciate your feedback.


    Thank you for contacting FamilySearch. It has been a pleasure helping you. Best wishes as you continue working on finding records for your family.

    1

Answers

  • BGPSW
    BGPSW ✭
    September 18, 2021

    I've noticed the same problem. It's not just on the residences but other details added during the merge as well, i.e. death date.

    In case it helps the engineers pinpoint the problem, this only happens when the reason field on the original detail was blank. If it was non-blank the original reason is preserved after the merge.

    0
  • Gordon Collett
    Gordon Collett ✭✭✭✭✭
    September 18, 2021

    This also seems to happen only to information brought over in the merge. So if you have the record on the right with the most information and do not need to move any information from the left side to the right, this does not occur.

    0
  • dontiknowyou
    dontiknowyou ✭✭✭✭✭
    September 19, 2021

    I am glad to know this novelty was not intentional. It is too much of a good thing.

    0
  • Mark.B.Hansen
    Mark.B.Hansen ✭
    October 16, 2021

    @CHold FYI. I reported this defect on 9/18, and as of today (10/16) it is still happening.

    0
  • Mark.B.Hansen
    Mark.B.Hansen ✭
    October 16, 2021 edited October 16, 2021

    Here is an example from today.

    image.png


    0
  • CHold
    CHold mod
    October 16, 2021

    @Mark.B.Hansen

    Thank you Mark, yes that issue is still being worked on by the engineers. I just checked that issue and as of October 5th they are still working on it they have many samples.

    Personally since I know this is still happening I go in and immediately edit the reason statement and delete it.

    Thank you for your patience.

    0
  • dontiknowyou
    dontiknowyou ✭✭✭✭✭
    October 16, 2021

    As I mentioned elsewhere, I now think this merge reason statement being "everywhere" is a good thing. A feature not a bug.

    0
  • Paul W
    Paul W ✭✭✭✭✭
    October 16, 2021

    Please let it be a bug!

    1
Clear
No Groups Found

Categories

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