Sync issues with MyHeritage OR RootsMagic 11
I've been using FamilySearch for a very long time. A few years ago, I started to actively use MyHeritage as well, and would periodically synс the trees between MyHeritage and FamilySearch.
A few weeks ago, after just a regular sync of my tree on MyHeritage, it only showed four people (me, my spouse, and the kids). The rest were disconnected from me. Since then, I tried everything and was never able to fix it.
I assumed this was an issue on the MyHeritage side, so I recently purchased RootsMagic 11, which has an option to sync the tree with FamilySearch. It still only syncs 4 people! Me and my immediate family.
I'm not sure what's going on, whether anyone has had a similar issue or knows how even to address it. I'm definitely connected to everyone in my tree. I can see in FamilySearch all of my parents and ancestors. But for some reason, the sync is broken.
Since the issue is now appearing simultaneously at both MyHeritage and RootsMagic, I realize it's an issue on the FamilySearch side. But not sure how to even address/fix it
Answers
-
Can you provide the PID(s) of the 'linking' profile(s) please, i.e. the most recent ancestors you'd expect to see but that aren't syncing? It's possible the profile(s) have a security setting that permits access from FS itself but not from the partner solutions, we have seen that before.
Thanks.
0 -
Absolutely!
Here are my parents for example: LN8W-V5N (deceased), LN8W-VYM (alive)0 -
I won't be able to see the living person but I will check the deceased one when I get back to my computer.
In the meantime, what happens if you do a RootsMagic import with either of your parents' PIDs as the start point rather than yourself?
0 -
Thank you so much for looking into it!
If I choose my parents (both my mom and dad), it gives zero.
If I try with grandparents, it works with some. So this is very interesting (and strange). For example, it starts to work with my first grandpa (2GZM-GFC) but doesn't with his wife (LN8W-VRY). Doesnt work with my second grandpa (LN8W-V5L) or his spouse (LN8W-VTM)
It seems like many of my ancestors might be affected (but it's hard to say then - which ones from other generations are being synced and which are not, even, for example, when we look at those names which are being synced starting from my grandpa (2GZM-GFC). I can't seem to figure out the easy way to figure out one by one who is being synced and who is not.0 -
Have you tried these imports starting with an empty RM database? RM import isn't good where there are already some people present in the same tree, it tends, infuriatingly, to give up far too easily and stop importing - I do get that it doesn't want to disrupt people's existing data without warning.
0 -
Yes, i only try and do it with the empty ones.
And again - this is not an isolated RM issue. The same issue is with the MyHeritage website…
1 -
I thought MyHeritage might be the same, but it all helps track these problems down ...
0 -
Thank you so much for offering the help. I hope there is a way to somehow figure this out. But just by looking at those entries about different ancestors i have - i don't see anything super different or similar, which would help to understand the cause of the issue.
0 -
OK. As I suspected, looks like the ones you can't import have this in their Person data:
"visibleToAll" : false,
"visibleToAllWhenUsingFamilySearchApps" : truewhile the ones you can import have this:
"visibleToAll" : true,
"visibleToAllWhenUsingFamilySearchApps" : trueThe question is why.
LN8W-VRY (false) was created as Living in 2012 by FamilySearch.
2GZM-GFC (true) was created in 2012 by FamilySearch, but with a death date.
LN8W-V5L (false) was created as Living in 2014 by FamilySearch.
LN8W-VTM (false) again was created as Living in 2014 by FamilySearch.
It looks to me as if this created-as-Living-by-FamilySearch scenario might be relevant to the (unusual) "visibleToAll" : false setting, but, Sergei, you could with advantage check a few more Change Logs to see if this correlation continues between import failure and created-Living-by-FamilySearch and between import success and not-created-Living-by-FamilySearch.
If useful, another thread discussing the visibleToAll setting is here:
Created-as-Living-by-FamilySearch doesn't look to apply there, though. It sounded on that occasion as if there was a privacy concern.
I will flag this post for moderator assistance with the new Other option.
0 -
Mandy, thank you again for looking into it!
can you please expand regarding this: “you could with advantage check a few more Change Logs to see if this correlation continues between import failure and created-Living-by-FamilySearch and between import success and not-created-Living-by-FamilySearch”
I’m not sure I know where to get this data from. I realize it’s probably hidden in the developers tools - but don’t really know where to look for those things0 -
Sorry, just go on to the Change Log (via 'show all' on the Changes section at the right hand side of the Details tab) for one of the profiles, go right down to the bottom and you should be able to see who created the profile, when, and whether Living on creation or not. No need for any developer tools.
If this doesn't explain it properly (I am on my 'phone at present so can't do relevant screenshots easily), please post again.
0 -
Mandy, thank you again! Seems like this is exactly what the issue is. Not sure why those are listed as created by FS. And not sure where to go from here.
Do you know what can be done in this situation to resolve this? Is there someone like a MOd/Support who can look and fix it?
I see one option of trying to create duplicates for those people and then merge these duplicates with the profiles which were created by the FS, keeping the duplicates as the remaining ones.
I only have a bit of a concern whether this will not jeopardize anything, like the temple ordinances and stuff. Any thoughts on this?Again- thanks so much for your willingness to look into it!
0 -
@Sergei Antamanov your duplicate/merge idea sounds worth trying.
Support/FS staff won't usually fix anything for us. Ordinary users are considered to be responsible for the maintenance of the Tree. The only exception I know of is where there has been really egregious abuse (for which the bar is insanely high). I am sure they'd also fix data corruption caused by a system failure of some sort, though I haven't seen that happen (could this strange handling of created-Living profiles possibly count?)
Meanwhile @Ashlee C. can you shed any light on this situation please?
0 -
@Sergei Antamanov Unfortunately, I can't offer much more than what has already been suggested. Privacy regulations vary across the world. FamilySearch adheres to existing legal requirements, which are a factor in this situation.
1
