When you migrate reference data assets, MDM SaaS uses internal IDs, aliases, and names to identify Reference 360 assets.
Guidelines to migrate Reference 360 assets
Consider the following guidelines when you import an existing asset:
•Ensure that the internal IDs of the imported and existing assets are the same. If they aren't same, Reference 360 creates a new asset.
•If the imported asset doesn't have an internal ID but has an alias, the alias must be the same as the internal ID or alias of the existing asset.
•If the imported asset doesn't have an internal ID or an alias, then the name of imported asset must be the same as the name of the existing asset.
•If an identifier of the imported reference data set is the same as the identifier of an existing reference data set, their default code lists must also match.
•If an identifier of the imported code lists is the same as the identifier of an existing code list, their reference data sets must also match.
•If an identifier of the imported crosswalk is the same as the identifier of an existing crosswalk, their source and target code lists must also match.
When you migrate assets, MDM SaaS uses internal IDs, aliases, and names to identify Reference 360 assets.
When you import an asset, Reference 360 first compares the internal ID of the asset that you import with the internal ID of existing assets. If the internal ID of the asset you import and the internal ID of any existing asset aren’t null and they match, the existing asset is successfully updated.
If the internal IDs don’t match and neither is null, Reference 360 compares the internal ID of the asset that you import with the alias of the existing asset, alias with alias, and then name with name. If any of these comparisons result in a match while internal IDs mismatch, the import fails.
If the internal IDs don’t match but either one of the internal ID is null, Reference 360 compares the internal ID of the asset that you import with the alias of the existing asset. If they match, the existing asset is successfully updated.
If they don’t match, Reference 360 compares the alias of the asset that you import with the internal ID and alias of the existing asset. If any of these values match, the existing asset is successfully updated.
If they don’t match, Reference 360 compares the name of the asset that you import with the name of the existing asset. If they match, the existing asset is successfully updated. If they don’t match, a new asset is created.
The asset migration fails if the names match but meet the following criteria:
•The assets have different aliases and no internal IDs.
•The assets have different internal IDs.
If no matches are detected, then Reference 360 considers the asset as a new asset and creates the asset.
For example, if the source asset is Cost Center with internal ID int_ccenter and the target asset is Cost Center Category with the same internal ID int_ccenter, Reference 360 compares internal IDs and updates the Alias and Name fields in the target system.
If the source asset is Cost Center with an internal ID int_ccenter and alias ccenter and the target asset is Cost Center Category with no internal ID and alias int_ccenter, Reference 360 compares internal ID and alias and updates the Name field in the target system.
If an asset with the same name but different IDs exists in both source and target, the import fails. Reference 360 considers to create the asset in the target, but a duplication error occurs and the import fails because an asset with the same name exists.
For more information about using the identifiers of assets to import the assets, see Internal IDs and aliases.