Mismatch in couple relationship - TreeShare

RootsMagic
1

I had posted in the fb RM users group a copy of an earlier discussion on the FTM users group about an issue with the Ancestry side having the couple relationship seemingly randomly flipping to “Unknown”. The FTMUG admin was surveying users (including any using RM) as an aid to FTM software developers to determine where the cause lay and how to fix it. I note now that the RMUG admin has removed the post which I think is unfortunate because there is an issue between RM and Ancestry over TreeShare in that the couple relationship setting on one side is not affected by changes on the other and, yet, a change is detected by the “Only show changed people” filter. However, there is no highlight of what has changed.

  • Could this be a contributing factor to why people sometimes see the “changed people” list grow but see no difference?
  • Might there be something going on over the API that is more than detecting a difference in the couple relationship settings? Might RM be triggering changes on the AMT end?
  • Is RM going to implement full support of couple relationships over TreeShare?

If you are also a FTM user you can see the full discussion at Family Tree Maker® Users | Facebook

2

Although this is an old topic, I want to continue on it. I am a user of FTM and RM and I have experienced the trouble mentioned by TomH.
Meanwhile, I found the reason of the trouble and fixed it, which was quite some task. The root cause of the problem found in FTM is treeshare from RM.
Here are my findings:

Starting with a minimal tree in RM containing only 2 persons : Father One and Mother One. The only fact they have is their marriage.

grafik
grafik373×186 24.7 KB

If I upload this couple by treeshare into an empty tree on ancestry, everything is fine.

But I do not know how to transfer this couple by syncing with treeshare to ancestry in an existing tree without introducing errors in ancestry that have to be corrected manually in ancestry.
The errors when syncing to an existing ancestry tree are:

  • introducing “unknown souse”
  • introducing marriage facts that are not connected to a partner (therefore the unknown souse)
  • changing the gender of the female partner to male if the marriage fact is uploaded later to an existing couple in ancestry.

Using syncing with treeshare there are 2 options to upload the partner:

One can add the spouse (Mother One) to the Father if choosing One, Father in the left row.
Or one can add a new person to the tree if choosing, Mother in the left row.

Both versions give the same result:

In ancestry Father One has a marriage fact, but this fact is connected to no spouse

grafik
grafik606×314 43.2 KB

In ancestry Mother One has a marriage fact, this fact is connected to the spouse

grafik
grafik605×396 56.3 KB

This means the data in ancestry is inconsistent. To evaluate further what happens in ancestry I downloaded this erroneous minimal tree from ancestry into an empty rootsmagic tree:

grafik
grafik605×418 51.9 KB

One can see two spouses: the correct spouse and another Unknown spouse with unknown sex.
Also, 2 Marriage facts. One is connected to the correct partner (Mother One), the other is connected to nobody, and this is the reason for the creation of the unknown spouse.

For Mother One there is no unknown spouse but 2 Marriage facts with different fact names: Marriage and Marriage-Spouse.

grafik
grafik606×415 51.9 KB

I can’t find a way to correct this mess in rootsmagic, but only in ancestry.

3

Another old but related post is this one: