Correcting Relationships in Family Tree
Just a thought ...
RATHER than COMPOUNDING an existing ERROR, which is very easy to do ...
One way would be to UNDO the ORIGINAL 'Merge"/"Combine"; and, start again.
Unmerge/Uncombine that which was done.
Then, start ALL over again with the "Merge"/"Combine", being careful as to WHAT is "Moving" OVER in the "Merge"/"Combine".
As was proffered by 'FamilySearch' ...
"Merging is a complex process in which you decide if two people are the same person. If they are, you choose which information should be kept. Please take the time necessary to carefully review each possible duplicate."
I am certain that MORE "Errors" are MADE through "Merging"/"Combining" than just about ANY other Part of "Family Tree" of 'FamilySearch".
Again, just a thought.
ps: I know, I have some experience with "Merging"/"Combining"; but, that said, I STILL make "Mistakes", sometimes, BIG ones.
If you have children added to a name via a merge that do not belong to that name, then there is an extremely high chance that you have merged two records of DIFFERENT persons.
You need to go back and correct the bad merge before proceeding with anything else.
I have just found out that it was not a merge,but my wife trying to be helpful inputing two children and attaching them to unrelated parents as she thought that they were the parents. So when trying to remove the 2 Children the parents are removed as well.
That is John Williams MXVD-J9Q and Mary Ann Greenwood MXVD-JCD parents
Children to remove Thomas Williams GH26-2V8
Sarah Ann Williams GH26- LQF
The other 3 children Elizabeth.Phoebe and Albert are ok
The editing of couple relationships and parent child relationships in the FSFT can be really confusing. I think that you were really close but just missed it 😊
First of all, since BlueMoonRose (I assume that is your wife) is the only one to have ever touched Thomas and Sarah, then SHE can go in and just Delete those two records (you cannot):
If you (or anyone else) touches either of those records (by editing a vital or adding a note, etc.), then even SHE will not be able to Delete them.
Since you cannot Delete the incorrect Thomas and Sarah records for that family, all you can do is remove the parent-child relationship between them and the John/Mary couple, leaving them to float in the database unattached to anything. Since the child is the common record to be removed from the parents, you would go to the CHILD's relationship and edit it using the little pencil and paper icon as shown above. Then select one of the items as shown below:
I know, I know. Why have two totally different appearing mechanisms to do the same exact thing? This is just one of the confusing things about how the relationship editing tool is set up.
In your case, the simplest is to just select the "Delete Parent-Child Relationship" button. But if you decide to go the long way and choose the "Remove or Replace (Child)" button, you get the following:
Note that the diagram is wrong as it shows the operation not only detaching Thomas from John and Mary, it also shows the couple relationship between John and Mary being deleted! Because of the confusion of the diagram, FS has had to totally spell out in detail what actually happens in the text below it. In any event, the "Remove Parents" text is correct and the diagram is wrong.
Also note that the SOURCE that is attached to the parent child relationship is the result of what appears to be new software trying to automatically populate the relationship entity. It is really confusing to try and manually remove it from the relationship because it keeps forcing you to try and search for the other "correct" Thomas (buggy). I can only assume that the source will be detached automatically when you delete the relationship. Since this appears to be new, I've not worked with it yet.
Anyway, try that, but when you are done you need to look closely at the source showing John and Mary's family. A quick check that I did appeared to have some other location inconsistencies for the other children in the family, but I'm not familiar enough in those locations to know for sure.