When you migrate reference data assets, MDM SaaS uses internal IDs, aliases, and names to identify Reference 360 assets.
Note: Effective in the April 2025 release, the ability to specify a unique internal ID and alias for a reference data asset is available for preview.
Preview functionality is supported for evaluation purposes but is unwarranted and is not supported in production environments or any environment that you plan to push to production. Informatica intends to include the preview functionality in an upcoming release for production use, but might choose not to in accordance with changing market or technical circumstances. For more information, contact Informatica Global Customer Support.
When you migrate reference data assets from one organization to another, Reference 360 uses internal IDs, aliases, and names to identify reference data assets.
When you import an asset, Reference 360 compares the internal ID of the asset with the internal ID of the existing assets.
If the internal ID of the asset doesn't match with that of any of the existing assets, Reference 360 compares the internal ID of the asset with the aliases of the existing assets. If the internal ID of the asset doesn't match with the aliases of any of the existing assets, Reference 360 compares the alias of the asset with the internal IDs of the existing assets. If Reference 360 finds a match but the internal IDs of the source and target assets differ, the import process fails.
If the internal ID doesn't match with any of the existing assets, Reference 360 compares the alias of the asset with the aliases of the existing assets. If Reference 360 finds a match but the internal IDs of the source and target assets differ, the import process fails.
If the alias of the asset doesn't match with that of any of the existing assets, Reference 360 compares the name of the asset with the names of the existing assets.
If the names don't match, Reference 360 creates a new asset. If any of the values match during this process, Reference 360 overwrites the existing asset.
Note: 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.
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.
For more information about using the identifiers of assets to import the assets, see Internal IDs and aliases.