I am trying to merge new information from a new tree into my existing Ancestry Tree but when I add the record using TreeShare all the information except Parent Child and Spouse does not get added.
-I down load my Ancestry tree into RM10
I created a new RM tree from the GEDCOM file with my new info.
-Opened both and copied all from the new file into the RM Ancestry file.
-At this point the merged RM file is exactly what I want to sync back to Ancestry with the new additions and links.
-Up loaded the RM file into Ancestry and manually added new records.
-The records are added except Parent Child and Spouse info
-Even after the records are manually linked and I manually add Parent Child and Spouse then accept changes they do not get to Ancestry
Just a thought here-- have you actually checked Ancestry to see if they were added?
Reason I ask is sometimes when I have added a person from RM to Ancestry, it still shows in tree share as I have not added them BUT when I checked Ancestry there were there…
Yes they are added but I loose all the links between people I have built in the RM data base. The data base I am trying to merge has about 200 people so a lot of wotrk to manually reconnect in Ancestry.
If I unlink and create a new Ancestry tree it works ok (all the new links are there) but then it is a new tree I need to relink to all my editors and viewers.
So my question stil is why TreeShare is adding people OK but not their relitives links.
I think what you have here are people linked to two separate Ancestry trees within the same database. Achieved by drag n dropping people from a database already linked to one tree into a database linked to a different tree. Only the tree you see at the top of the Ancestry TreeShare will be shown on the Ancestry side, even though the people still appear linked to someone on Ancestry which technically they are. This issue has been reported to development.
The only way I can think to fix it is to remove those added still linked to the “new tree”. Then make a copy of the “new tree” database they came from and disconnect it from the Ancestry tree. (Settings, WebHints, Disconnect from Ancestry tree) Once disconnected you can drag n drop the same people to the existing database and add them to that Ancestry tree.
Thankyou for your feed back but I only partly agree with your analysis.
The RM data base I am trying to up load was created by downloading an Anscestry database and is linked to that.
The data I added is NOT linked to any data base it is just raw data imported from a GEDCOM data base.
When up loading it is just the added links data from the GEDCOM import that are not properly uploaded.
Your second point is true. If I unlink the Ancestry data base and up load to create a new Ancestry tree all the links up load just fine.
So modifying a Ancestry data base with TreeShare is not working in this case but creating a new one is ok.
Only issue with creating a new data base is my co-editors and viewers lose their access. I may need to resort to this work around … stop their development… then re-link them after the full rebuild.
Problem is when i dont use the “Dicsonect from Ancestory” setting and try to update existing Ancestry Tree. When I use the “Dicsonect from Ancestry” setting RM creats a new tree and the problem is not in the new tree. (But I dont want a new tree since ther are common editors using the original tree)
One Ancestor tree created one RM data base then I import from a GEDCOM data base and try to up date the Ancestry Tree using TreeShare
The people Data was down loaded from “Family Search” (in pieces) to RM where it built a new GEDCOM file.
(If you have worked with “Family Search” you will learn it does not support GEDCOM down loads. Thankfully RM can take this data and successfully build a GEDCOM data base)
So to sumerize I downloaded my Ancestry tree to RM. Imported a GEDCOM created from “Family Search” then up load back to Ancestry. But no family links from the GEDCOM got uploaded.
BTW: If you feel this issue should be reported to development I can supply the data bases and instructions to reproduce the problem if they would like it.
Getting late for me, so I will look at your answer tomorrow
BUT I don’t think that is your problem at least not now…
I added 4-5 people to my database twice today-- tree shared the group each time and it worked just fine.
Your 1st screen shot shows Waleria in there once, the 2nd screen shot shows her in there twice and the 3rd goes back to one BECAUSE YOU manually link them as I understand…,
Your screen shots show you have Show Everyone INSTEAD of
ONLY SHOW CHANGED PEOPLE CHECK–so check that and you should see a list of all who still need to be added
Add the 1st one and they will fall off the list-- then add the next until you have completed the list-- the last person will NOT be shown anymore on the CHANGED LIST side BUT will still be on the right side of page…
I clicked on Options and selected Clear everyone from list then closed that screen and tree shared again and it shows no one…
I just tree shared all 5 of the people above and there are all listed on Ancestry and linked together…
There is no way to accept all changes at once-- this is why most people will tree share every time they add abt 50 people because it is one at a time
here is a video-- except for the signing in / 2 step verification and using RM 9 or 10 only, it works basically the same
The steps just don’t make sense for why its showing people linked and it cannot show the person on the Ancestry side. I would assume you disconnected from the Ancestry tree before uploading it to a new Ancestry tree. Open a support ticket and include a backup of your database and the GEDCOM used. You will need to share the Ancestry tree with Editor permission with the support agent.
I found if I manualy modify the record in the RM data base after the GEDCOM is imported and try an up load it now gets recognize as a changed record .
Some times the Add button creates a proper matched link but some times it still does not . Cant figure out why or why not sometimes.
I will open a ticket and provide the data to reproduce the problem
