After the recent RootsMagic update besides noticing a very sluggish sync process I’ve also noticed that I’m finding that a few people I merge/delete on Rootsmagic keep popping up on the Ancestry side when I resynch. It appears to be the same 5 individuals popping up that I delete within the Treeshare window but when I exit and enter Treeshare later they still appear. I’ve done this about 4-5 times with no luck. I’m continuing to update and make corrections on the Rootsmagic side and resynch and all the updates appear to make it across to Ancestry but these 5 individuals keep popping up. I hope I’m explaining myself clearly. Any thoughts on what could be happening. Are Rootsmagic and Ancestry still working out the bugs on the new API. Should I just ignore the issue and plod along.
Did you delete them on both RM and Ancestry? Check both and see which is remaining where.
Normally what I do when I find a duplicate on my Rootsmagic file I merge them than do a synch and then use the treeshare window to delete the duplicated record on the Ancestry side.
It appears to take but when I reenter Treeshare later the same 5 indiv still appear on the Ancestry side. I maintain my Ancestry database as the primary database and then always use Treeshare to remove the duplicated indiv on the Ancestry side. I’ve been doing this for quite sometime but only encountered the issue of these 5 records not being delete/removed from the Ancestry side since the last 1-2 updates.
I just went on the Ancestry site and searched for the 5 indiv and couldn’t locate them in the Ancestry file. Weird. But when I start up Treeshare it appears that Rootsmagic sees them in error as appearing on the Ancestry side even though they don’t appear on my Ancestry tree when I access it directly. I’ve also entered the Tools section and ran all the Database tools against my Rootsmagic file and the problem still exists. Any suggestions?
I’ve went thru the same process a few minutes ago of identifying some duplicates on Rootsmagic and synching and deleting the indiv within the Treeshare window and when I entered Treeshare again I found some of the indiv are gone but some of them are still sticking as appearing to be listed on the Ancestry side but when I search Ancestry online they aren’t there. I’ve now got 8 indiv/items that appear to be phantom records. It seems to be hit and miss as to which merge/deleted items that stick around.
Can you give me a screen shot?
From experience I would recommend that if you’ve already synced the tree to Ancestry that you merge the people in RM, then also merge the people in Ancestry (select show Ancestry when doing TreeShare, then merge duplicate). You’ll likely have to exit TreeShare and reenter to see if you need to update or link.
Fix them in RM (don’t TreeShare yet) PLUS fix them in Ancestry.
Now try TreeShare.
I’ve had this happen and this was the fix.
I don’t really get it. I’ve been Merging RM duplicates and then Treeshare and removing the Ancestry dups via Treeshare for quite sometime and have only run into these phantoms in the last day or so after the RM updates. It would be pretty cumbersome having to merge both RM and Ancestry dupes before running Treeshare. I thought Treeshare is the tool that allows you to deal with these dups easily 
I’ve uploaded my RM file to Ancestry a few months ago and have recently been using their Tree Checker Tool which has identified possible 7500 dup/errors in my family file. I’ve worked my way thru the surnames beginning from A thru C without any issues until the last few days. So my I’m just wondering if the new API update on Ancestry may have introduced a possible bug.
When I use the TreeShare ‘Show on Ancestry Button’ I get ‘We’re sorry, this page is temporarily unavailable error page on Ancestry. If I check directly on Ancestry to see if the merge/deleted individual still resides in the Ancestry file they don’t appear when I search Ancestry. But when I initiate Treeshare the merged/deleted dup appears in the TreeShare window in the Ancestry panel.
I’ll try to put a few screenshots together for RM and see what they have to say about it.
Thanks again for the suggestions. Cheers!
If this is the case, I would skip using TreeShare until you fix All OR the majority of dups, then upload a New Ancestry tree.
IMHO you have bigger problems with your database then just Treeshare.
Helle Renee,
Please find enclosed screenshots outlining the steps I’m taking to delete duplicates. The duplicates outlined in the Ancestry pane of the first Treeshare are individuals that I had previously merged within RootsMagic.
When I run Treeshare see Pic 1 it identifies Ancestry dups that I have all ready merged/deleted within RootsMagic
Pic 2 shows deleting Ancestry dups from Treeshare
pic 3 ReSynching Treeshare after deleting dups
pic 4 Ancestry lookup for deleted dup
pic 5 Treeshare Ancestry lookup of dup
Like I’ve said previously I’ve been doing this for quite some time but since the last two updates I haven’t been able to remove these individual dups. Its like some kind of synch record has been lost as I cannot find these dups on either my RootsMagic file or on my Ancestry site. Any thoughts. I’m thinking I’ll have to start over sometime in the future uploading my whole RootsMagic file to Ancestry. But at the moment I’ll just have to just ignore these records while I continue to use Ancestry’s Database Tools to identify dups in my RootsMagic file. I’ve been using the Ancestry Database tools to identify duplicate candidates then locate them in my Rootsmagic file and then merge/delete. I then run Treeshare to remove the identified dup from the Ancestry side.
Its been working quite well. I just don’t want to have to reload my RootsMagic file to Ancestry and have start from the beginning as I’m only about a 1/5 the way through the identified Ancestry listing of 7543 potential dups (7453) in my RootsMagic file of 178k individuals.
