FS Person Tools still pointing at deleted person after merge using FS direct

When using FS directly to merge duplicates, if the FSID known to RM is deleted during a merge, the FS Person Tools panel is still using the old deleted FSID. The only way to tidy up is to use the Person Tools to unmatch and then search for a match and match with the new FSID.

Is anyone else seeing this behaviour as it seems a recent change? I’m an active FSFT user and I’m sure RM used to handle this sort of situation and adjust to the new FSID. This certainly isn’t happening now.

(Using RM 1.1.1 on a Mac.)

depending on what happen in RM – you can have more than ONE person (RMID) but have the same FSID. Meaning you could ending up with multiple RMID to same FSID. You can find them RM by using grid view with that column etc There is not a simple way to display FSID having count > 1 by RMID within RM

Confirming issue has been reported to development.

1 Like

That is rather different. I have one RMID pointing at one new FSID, and then, having used FS to merge that one new FSID into a different (old existing) FSID, so the new FSID is deleted on FS, the RMID still points to the deleted new FSID even though I re-access the RMID person or their parents.

So basically what you are saying when if/when a merge on FS side occurs and RM knows about the original one the table may still point to the “old”/original FSID (in RM db) that FS ID from RM POV still thinks is valid? (not sure if best said)

Yes I have seen that happen also – however I have seen when an FS ID has changed it will get changed and point to the the new “result FS ID” but this is rather transparent when / if occurs and confusing in the RM FSC panel – so in any case this is rather confusing but should be flagged and maybe a popup “FS ID has changed or no longer valid” – You make a valid point

Yes, I think we agree on the problem description (though not that easy to explain).

My point is that although I had seen this issue long long in the past, it is a very long time since I experienced it, but it now, at 1.1.1, seems very repeatable.

I do a lot of adding MY people to FS using RM and then merging them into duplicates using FS direct. When I have a lot more of the vital info entered for MY person than any of the FS duplicates, that saves a lot of individual fact updates, so less effort. Usually MY person ends up being deleted by the merge in FS, though not always - depends on the merge order.

1 Like

yes agreed/understood. I have noticed that it depends - at least previous to more recent version (I have not witnesses yet with more recent) – RM will usually switch FSID to new “Surviving FSID”