You can define a reference data export job to export code lists, crosswalks, and hierarchies from Reference 360 data store to an external data source.
Prerequisites for exporting reference data
Before you export data, ensure that you complete the following prerequisites:
1In Administrator, create a Business 360 connection to read data from Reference 360 and a target connection to write the data to an external data source. For more information about creating connections, see Configuring a connection in the Administrator help.
Note: You cannot use same connections as source and target for reference data export jobs.
2In Administrator, specify a Secure Agent that is up and running as the runtime environment to run a mapping task. For more information about Secure Agent, see Runtime environments in the Administrator help.
3In Cloud Data Integration, create a mapping with the Business 360 connection as the source transformation and the target connection as the target transformation. Select code lists, crosswalks, or hierarchies from Reference 360 to specify the source object and select Map all descendants for the root element to define field mappings. Select root as the output group. Ensure that you create an in-out parameter jobInstanceId in the Parameters panel. For more information about creating a mapping, see Mapping configuration in the Data Integration help.
The name of the in-out parameter is case-sensitive.
4In Cloud Data Integration, select the runtime environment to create a mapping task. Add the mapping that you create to the mapping task. For more information about configuring a mapping task, see Mapping task configuration in the Data Integration help.
5In Cloud Data Integration, create the required taskflow. Publish the taskflow to use in the reference data export job. For more information about creating taskflows, see Taskflows in the Data Integration help.
Rules and guidelines for reference data export jobs
Consider the following rules and guidelines when you export reference data, such as code lists, crosswalks, and hierarchies, into Reference 360:
•Before you run the reference data export job, ensure that you publish the taskflow in Cloud Data Integration.
•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 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.
Export types
You can export code lists, crosswalks, and hierarchies to an external data source. You can choose to export all data or only incremental data after you export all data for the first time.
You can use any one of the following export types:
Standard export
Exports all the data in the first run of the job and then exports the data that are added or updated after the first run incrementally based on the job schedule.
For example, you add 30 code values to a code list. During the first run of the job, the job exports 30 code values. After the initial run of the job, you update 15 code values to the code list. During the second run of the job, the job exports the last updated 15 code values.
Custom export
Exports all the data added or modified after the specified date in the first run of the job, and then exports the data that are added or updated after the first run incrementally.
For example, you add 20 code values to a code list after January 18, 2022, 5:00 p.m. During the first run, if you specify January 18, 2022, the job exports the 20 code values added after the specified date. After the initial run of the job, you update 10 code values. During the second run of the job, the job exports the last updated 10 code values.
Export all
Exports all the data in each run of the job.
Export reference data
Before you create a reference data export job, ensure that a taskflow is created and published in Cloud Data Integration. You can create the reference data export job to export data from Reference 360 data store to an external data source.
When you use Cloud Data Integration to export data, you can export the following additional attributes of a code list:
•Last updated date
•Last updated by user
•Created date
•Created by user
•Last updated date of parent relationship
•Last updated by user of parent relationship
Note: You can export the last updated date of parent relationship and last updated user of parent relationship attributes only for hierarchical code lists.
1Click New > Jobs > Reference Data Export > Create.
The Reference Data Export dialog box appears.
2Specify the following job properties:
Property
Description
Display Name
Name of the job.
Internal ID
A unique job identifier, which is generated based on the display name that you enter. You cannot change the internal ID after you create the job.
Description
Optional. A brief description of the job.
Location
Project or folder within which you want to save the job.
3Click OK.
The reference data export job page displays the process, description, and export type.
4Select one of the export types.
For more information about export types, see Export types.
5To add a taskflow, perform the following tasks:
aClick Add Taskflow.
The Select an Asset page appears.
bSelect a taskflow, and click Select.
The taskflow appears in the Taskflows section and the associated assets display in the Assets section.
Note: Ensure that the taskflow is published before you run the reference data export job.
6Click Save.
7To run the job, click Run.
You can monitor the status of job on the My Jobs page.