Reference data export job

Import code values

Migration of reference data assets

Creating reference data assets

User interface

User interface element	Current behavior	Previous behavior
Filter in the History tab of assets	The filter options now appear when you click the Show/Hide Filter icon. The following image shows a sample code list that highlights the Show/Hide Filter icon: The following image shows a sample code list that highlights the Filter options:	Previously, the filter options appeared within the Filters panel.
Date Range in the History tab of assets	You can now view the date range option within the filter options. The following image shows a sample code list that highlights date ranges available within the filter options:	Previously, the date range option appeared as a field.
View option in the History tab of assets	The View option now appears as an icon. The following image shows a sample code list that highlights the View icon:	Previously, the View option appeared as a field.
Create a crosswalk	When you create a crosswalk, you can specify the general properties of the crosswalk on the Summary tab.	Previously, you could specify the general properties on the New Crosswalk window.

REST API

model version 3

The model version 3 REST API now uses identifiers, such as internal IDs, aliases, and names, to identify reference data assets during asset migration.

To successfully compare and import reference data assets, identifiers of imported assets must match existing assets. This includes that default code lists must match for reference data sets, reference data sets must match for code lists, and source and target code lists must match for crosswalks.

Previously, reference data assets were considered a match if their names matched even if their default code lists were different.

For more information about the model version 3 REST API to import and export reference data assets, see

Reference 360 REST API

.