Use this resource to generate aliases for existing predefined assets that you created before the April 2025
release based on their names. These assets don't have internal IDs configured, so you can use
this resource to create aliases that function as alternative identifiers for these assets. The
alias generation API runs an alias generation job. You can retrieve the status of the alias
generation job.
When you migrate assets that don't have internal IDs,
Reference 360
uses aliases to identify
them. Additionally, generation of alias identifies existing predefined assets created before the April 2025 release
that don't contain internal IDs.
You can't generate aliases for assets that are in the draft state. Before you run the alias
generation REST API, ensure that you publish these assets.
To run the REST API, a user with the Reference Data Management Basic Edition license must be
assigned the MDM Designer role.
To run the REST API, a user with the Reference Data Management full license must be assigned
one of the following roles:
Reference 360
Administrator.
Reference 360
Primary Owner to
update reference data sets and code lists.
ASK INFAPreview
