How Can We Help?
Merge Persons and Synchronised DataMerge Persons and Synchronised Data
What
If you have duplicates in your Pure, you can choose to merge them. If you merge duplicate Persons you might have a new merged version with both synchronised and not synchronised data.
Why
- The fields that are not synchronised appear on content because the data is not connected to an active synchronisation. In order for the data to be locked, it must be part of the source data and in an active synchronisation.
- Pure unlocks the data when merging, to avoid the data being permanently locked.
- If your source data still provides data for the organisation affiliations in question for the merged Person, then they will be picked up by the synchronisation and locked again.
- When you merge a Person it is important to choose the correct target. Use the Person as a target, which has the primary IDs connected to your synchronisation source data.
- If you merged the Person incorrectly, you can switch the Source IDs on the Person or if the Person are missing an ID you can add it.
- Change or add the Source ID on the Person in the editor window > External sources.
- Click Save.
- If you merged the Person incorrectly, you can switch the Source IDs on the Person or if the Person are missing an ID you can add it.
- The synchronisation framework supports syncing data from two or more IDs.
- The metadata from the source will be pulled from the primary ID and organisation associations will be fetched based on all the IDs.
Note: The synchronisation only supports multiple IDs for organisation associations. - Everything in the synchronisation is managed by IDs. These are the Source IDs on the Person but also Source IDs on any associations such as Organisation affiliations, Titles, Links etc.
- As long a you do not change any IDs in the source data, the synchronisation will not create duplicates but rather pick up and update existing content in Pure.
- Any new data added with a new ID will trigger creation of a new affiliation.
More information
KB-141 Person not associated to User
Note: Some of this information is for internal use only and might not be accessible.
Updated at July 27, 2024