If data has been imported in to RM which contains Unique Ids, using TreeShare in RM9 the Unique Ids were uploaded to Ancestry. I’ve upgraded to RM11 and have found that they are not being uploaded. There are crucial to the way I work! Why has this been dropped?
Because Ancestry owns the API and dictates what can be uploaded and downloaded. RM can only comply or stop using the API.
How do you know that it isn’t supported in the api and it’s just that RM haven’t used it in the rewrite of TreeShare?
That makes no sense! RM clearly has not re-written TreeShare. I also can’t imagine a scenario where RM purposely stops uploading data with Ancestry being involved by changing the API.
If you are so reliant on Unique IDs, that is your issue to resolve. You either need to find a new workflow or stop relying on UIDs. I am assuming that since you seem to use FH7 as your primary program, this has to do with needing RM to get your data to Ancestry.
Can you be more specific about the change - what field and source template do the unique IDs appear in and where did this field used to get mapped to on ancestry?
Nothing to do with fields or sources, they a globally unique identifier created and formatted as specified in RFC 4122. They are attached to individuals in the RM database but not visible in the gui. When uploaded to Ancestry (either by pre RM11 TreeShare) or by uploading a GEDCOM containing them, they are not visible on the Ancestry website, but when you download a GEDCOM from Ancestry they are there.
1 Like
That makes no sense! RM clearly has not re-written TreeShare. I also can’t imagine a scenario where RM purposely stops uploading data with Ancestry being involved by changing the API.
If you are so reliant on Unique IDs, that is your issue to resolve. You either need to find a new workflow or stop relying on UIDs. I am assuming that since you seem to use FH7 as your primary program, this has to do with needing RM to get your data to Ancestry.
Ancestry is discontinuing the api RM have used until now. Although the interface looks the same there will have been a substantial rewrite of the code behind the scenes to interface with Ancestry. I think it unlikely that the new API does not include provision for UIDs and it’s that RM have overlooked the need to upload them.
I see. Probably best to open a support request on Monday. It could be an oversight as you suggest. I don’t do much with gedcom’s but I noticed that the ancestry gedcom does contain their person identifier that rm places in the AncestryTable.anID field. Worst case, you could query the RM PersonTable.UniqueID from that. I realize that’s not the answer you are wanting but it could be a workaround if there’s no other option.
Thanks. I’d already identified that as a possible workaround. Not going to do anything until I hear back on the ticket I’ve raised.
1 Like
There’s a possibility that since RFC 9562 has now superseded RFC 4122 and has been adopted for the proposed GEDCOM 7 spec…
You might experiment with that as your UID basis. Just a thought.
1 Like
The newer RFC just updates how the UID is generated. That’s irrelevant if RM is going to lose it when uploading to Ancestry!
@rzamor1 I’ve raised request #151750 for this issue. Are you able to say whether this will be fixed or do I have to think of changing the process I use?
1 Like
I just finished testing the issue and replied back to you.
@rzamor1 I’m not sure why you looked at an earlier RM 11 version when I said I had upgraded from RM9.
It is easy to reproduce. Save this as a GEDCOM:
0 HEAD
1 SOUR Family Historian
1 GEDC
2 VERS 5.5
2 FORM LINEAGE-LINKED
1 CHAR UTF-8
1 DEST GED55
0 @I1@ INDI
1 NAME John /Doe/
1 SEX M
1 DEAT Y
1 _UID 093C975EDB2D48409522F7100689992ADA1E
0 TRLR
Create a new RM 9 file by importing the GEDCOM. If you use an Sqlite DB browser and look in PersonTable you will see RM has imported the UID stripping the hyphens and adding the last 4 checksum characters. Use TreeShare to create a new tree in Ancestry and then export the tree from Ancestry. This is the GEDCOM produced:
0 HEAD
1 SUBM @SUBM1@
1 SOUR ``Ancestry.com`` Family Trees
2 NAME ``Ancestry.com`` Member Trees
2 VERS 2025.08
2 _TREE UID Test RM9
3 RIN 210339678
3 _ENV prd 2 CORP ``Ancestry.com``
3 PHON 801-705-7000
3 WWW ``www.ancestry.com``
3 ADDR 1300 West Traverse Parkway
4 CONT Lehi, UT 84043
4 CONT USA
1 DATE 29 Apr 2026
2 TIME 17:44:59
1 GEDC 2 VERS 5.5.1 2 FORM LINEAGE-LINKED 1 CHAR UTF-8
0 @SUBM1@ SUBM
1 NAME ``Ancestry.com`` Member Trees Submitter
0 @I142768480414@ INDI
1 NAME John /Doe/
2 GIVN John
2 SURN Doe
1 SEX M
1 UID 093C975EDB2D48409522F7100689992A
0 TRLR
Repeat the same process using RM 11 and you get this GEDCOM from Ancestry:
0 HEAD
1 SUBM @SUBM1@
1 SOUR ``Ancestry.com`` Family Trees
2 NAME ``Ancestry.com`` Member Trees
2 VERS 2025.08
2 _TREE UID Test RM11
3 RIN 210340077
3 _ENV prd
2 CORP ``Ancestry.com
3 PHON 801-705-7000
3 WWW ``www.ancestry.com
3 ADDR 1300 West Traverse Parkway
4 CONT Lehi, UT 84043
4 CONT USA
1 DATE 29 Apr 2026
2 TIME 18:14:27
1 GEDC
2 VERS 5.5.1
2 FORM LINEAGE-LINKED
1 CHAR UTF-8
0 @SUBM1@ SUBM
1 NAME ``Ancestry.com`` Member Trees Submitter
0 @I392775608432@ INDI
1 NAME John /Doe/
2 GIVN John
2 SURN Doe
1 SEX M
0 TRLR
If you look in PersonTable you will see RM 11 has the same as RM 9.
BTW, I am aware of a number of other people who are using the same process as myself and currently on RM 9 or RM 10. Not sure they will be paying to upgrade if this can’t be fixed.
Just found something else. If you create a new RM 11 file by importing a GEDCOM which doesn’t have any UIDs, then looking in PersonTable RM creates one itself.
RM11 definitely creates a .LST file with a GEDCOM import error:
Unknown info (line 28)
1 UID 093C975EDB2D48409522F7100689992A
Record Identifiers in GEDCOM: RID, SSN, AFN, RFN, REFN, IDNO, RIN & _UID
I’m not sure what point you are trying to make when you have changed the contents of the GEDCOM from what I posted!
If you have the GEDCOM exactly as I posted (with the leading _) there is no error and the UID is imported to the PersonTable.
No, I didn’t change anything. I was picking up from where You said This is the GEDCOM produced: and merely reflecting that the produced GEDCOM has a clean (no underscore) UID tag which RM11 does not recognize (in GEDCOM vernacular). And the Tamura Jones page link has her saying "While Ancestry Family Tree Maker supports _UID , Ancestry(dot)com uses UID (no underscore) instead."
1 Like
I wish you’d made it clear that you were referring to the results of importing the GEDCOM produced by Ancestry, not what happens when you import the sample I gave in to RM.
The process I use for the GEDCOM produced by Ancestry recognises either UID or _UID whereas RM doesn’t so that is perhaps a separate issue that you may like to take up with RM.
What is crucial to me is that when RM is given a UID in a format it recognises, TreeShare uploads it to Ancestry.
1 Like