Specify record update preference

You must specify how records from the file must be updated in the tenant.

This task allows you to specify the record update preference. When you click CONTINUE after mapping, you are prompted to specify the record update preference as follows:

Note: If any of the attributes or columns are missing, full update can cause the attributes to become null values. Therefore, partial update is used as the default value for update preference to prevent any data loss.
The various advanced options for dataload that affect how the existing data is overridden, are explained as follows:
Note: The preserveHidden options are enabled only when the DCR is enabled.
For more information, see Create Entities.
  • partialOverrideForReference: The option is used for POST /entities (override entity) request. If the value is true, all attributes are overridden. The attributes that are not involved with referencedAttributeURIs,are not used.
  • updateAttributeUpdateDates: By default, this option is disabled. When the singleAttributeUpdateDates property is present, the property of crosswalks is updated. The property is modified for new and updated attributes if
    • There is an override of an entity
    • When a match with an existing entity is found
The singleAttributeUpdateDates property allows you to store the dates when each entity attribute is updated. By default, this date is not saved if the entity is overwritten. It is assumed that the dates on which all attributes are updated are equal to the last date when the crosswalks and the related attributes are updated.
  • preserveHidden: If the option is specified, the API does not create a Data Change Request (DCR) to delete the hidden attributes when these are not specified in the request.
  1. Select Full Update or Partial Update.

    For example, a record exists in the Reltio platform with five attributes but the file that is being loaded, only has three out of those five attributes. In this case, if you select:

    • Partial update: Only those three attributes will be updated and the other two missing ones will be left as is.
    • Full update: The provided three attributes will be updated while the remaining two since they were missing will be nulled out.

    By default, the Execute LCA option is enabled which means that the LCA data is loaded during data load. You can disable this option if you do not want to load LCA data during data load. There are scenarios where customers want to disable LCA during the initial data load before go-live. This is to check the behavior of the tenant and data without LCA to ensure that there is no impact because of LCA related issues. In such cases, you can disable this option data during data load.

    There can be a scenario where you want all activities in the Reltio tenant to go through a workflow to ensure that a process of review and approval is followed. For example, you might want to create entities only through a data change request. To enable such requirements, the Data Loader includes a parameter called Enable Data Change Request (DCR). If you enable this parameter while loading data, a DCR is created for each entity that is loaded and the entity is loaded only after the DCR is approved.

    Note: This parameter is only available for tenants that have Workflow enabled. In addition, the user loading data must have permissions to create DCRs and be able to start the DCR workflow process. For more information, see Start a Process Instance. The number of DCRs that can be created with the job is limited to 1000. If this number is exceeded, the job fails with an error. For more information about DCRs, see Reviewing Data Changes.

    If you enable the new DCR option, data is not loaded directly. You must click on the SUGGEST DATA LOAD button on the review screen instead of the LOAD DATA button that appears for the non-DCR data load jobs. You are directed to the Job Status page and the job appears under the PENDING tab. A blue color DCR icon appears on the top right of the job definition to indicate that the job will create DCRs instead of loading data directly as shown as follows:

    After a job is complete, the job definition moves to the COMPLETED tab. When you click on a completed job definition and click on the DETAILS tab, new fields added under Job Information appear. The value of the Data Change Request field is Yes and the DCR created field shows the number of DCRs created. In addition, you can click on the link to navigate to Reltio Inbox to view the DCRs that are created.

    The page displays the Mapping Summary, Job Information, and File Details.

    If a job completes with an error because the number of DCRs exceeded 1000, you can mouse over the job definition to view the error description as follows:

    Click on a job definition that failed with errors and click the DETAILS tab. You can view the number of failed records and download the error file that is in CSV format.

    The Completed tab on the Job Status page displays the following record statistics that explains the number of loaded, failed, and empty records in each job.

  2. Click Recurring Job Definition and specify the schedule as required.
    Note: Scheduling is not available if the input file is loaded from the local file system.

    In the following example, the job is scheduled to run every Sunday on a weekly basis.

  3. Click CONTINUE.
    The Review page displays the file details, mapping summary, and job information. You can edit the mapping or the record update preference if required by clicking Edit mapping and Edit job respectively.

  4. Click SAVE AS DRAFT or click LOAD DATA or SUGGEST LOAD DATA to load data or request a data load respectively.