Before you run the reference data import job, ensure that you publish the taskflow in Cloud Data Integration.

After you add a taskflow in Reference 360, don't rename the code lists, crosswalks, and hierarchies that the Cloud Data Integration mapping uses. If you rename the code lists, crosswalks, and hierarchies, the reference data import job fails.

After you create a mapping in Cloud Data Integration, if you rename an asset that's associated with the mapping in Reference 360, manually update the mapping in Cloud Data Integration.

Ensure that you don't rename a code list that's associated with a mapping in a source organization if the target organization has the same code list.

Ensure that the Code fields don't contain leading or trailing spaces. Reference 360 uses the Code field values as source primary keys for code values. If the Code field values contain leading or trailing spaces, Reference 360 ignores these spaces in the source primary keys. When you update the code values, Reference 360 fails to create relationships because of mismatches between the Code field values and the source primary keys.

Ensure that the name of an asset you use in a Cloud Data Integration mapping doesn't contain a slash

(/)

. If the asset name contains a slash

(/)

, you can't view the asset in Cloud Data Integration.

Before you import a child code list, use a separate reference data import job to import its parent code list. If you use the same job to import both the code lists, the load step fails.