In CET unable to select Possible Match Found
Comments
-
This is a thing I just experienced too. It seems it's accidentally finding you a potential match to a person you're trying to add into your private tree …from the Tree. Problem is they're different trees, so as soon as you say "sure I'll add that person" it can't let you actually do it. It should probably either be removed as a feature entirely from CETs or changed to allow you to duplicate Tree individual profiles when adding people to CET (creating/adding a replica of that profile, not adding/connecting that actual profile) — or you could also use it to prompt you if there's already a person in your CET connected elsewhere (useful for people with multiple relationships within a tree) that matches what you've entered, in case you forgot that person's already in your CET and didn't go to the "someone already in my tree" option like you should have.
0 -
J,
You are absolutely correct that person matches should not cross tree boundaries like that. These should not be shown and I will alert the match team that why are.
The data model prohibits the adding of a PID from one tree into another tree, as you discovered.
We will soon be releasing Tree2Tree matches and a new tool that will facilitate the comparison of data in one tree and matching people in another. It will allow the copying of data between PIDs, and if a person needs to be copied from one tree into the other a new "recipient" PID will be created and the data from the matched tree will copied onto it.-Robert Kehrer, sr product manager
0 -
@Gary Romsaas @J Purkaple Thank you for testing early access CET and giving feedback. As mentioned by @Robert Kehrer, Tree2Tree is a new feature that will facilitate copying information from one tree to another across all FamilySearch trees. Watch this group for news about that feature being put into production. Thank you, again,
0 -
Thank you for bringing this to our attention. We’re committed to resolving as many issues as possible, and we’re closing this discussion for now. If you or others encounter this issue again, please start a new discussion and include relevant information such as your operating system, browser, URLs, and screenshots if available.
We appreciate your support and engagement. Please don’t hesitate to reach out with any future questions or concerns.
0
