Specify record update preference
Learn how to specify how records from the file must be updated in the tenant.
preserveHidden options are enabled only when the Data
Change Request (DCR) is enabled.partialOverrideForReference: You can use the option forPOST /entities(override entity) request. If the value is true, all attributes are overridden. The attributes that aren’t involved withreferencedAttributeURIs, aren’t used.updateAttributeUpdateDates: By default, this option is disabled. When thesingleAttributeUpdateDatesproperty is present, the property of crosswalks is updated. The property is modified for new and updated attributes if- There’s an override of an entity
- When a match with an existing entity is found
singleAttributeUpdateDates property enables you to store the
dates when each entity attribute is updated. By default, this date isn’t saved if the
entity is replaced. It’s 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 doesn’t create a Data Change Request (DCR) to delete the hidden attributes when these aren’t specified in the request.
- 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 remain intact.
- Full Update: The provided three attributes will be updated while the remaining two will be nulled out. since they were missing.
When you select Full Update, you must map all required attributes of the target entity type of the job. If you haven’t selected all the required attributes, you'll see the error dialog. On clicking the Continue button if one or more mappings of the required attributes are missing. This will prompt you to either return to the previous page and map all the required attributes or update to the Partial Update for the job.
You can continue with Full Update, but the new entities won’t contain the missing attributes.Note: If one or more mappings of required attributes is missing and you still want to continue with Full Update, the existing values in the missing attributes will be replaced with these empty values.
For more information, see Map File Columns to AttributesBy default, the Execute LCA option is enabled. This indicates that the LCA data is loaded during data load. You can disable this option if you don’t want to load LCA data during data load. There are scenarios where users want to disable LCA during the initial data load before go-live. You can check the behavior of the tenant and data without LCA to ensure that there’s no impact because of LCA-related issues. In such cases, you can disable this option data during data load.
You may want all activities in the Reltio tenant to go through a workflow process. This is 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 About Data Change Request.If you enable the new DCR option, data isn’t loaded directly.- Select the SUGGEST DATA LOAD button on the
review screen instead of the LOAD DATA
button.
You can see the LOAD DATA that helps you in the non-DCR data load jobs.
You’re directed to the Job Status page. You can see the job under PENDING tab. You can see a blue color DCR icon 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. - Select a completed job definition.
- Select the DETAILS tab.
You can see that the new fields added under Job Information.
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 select on the link to navigate to the Reltio Inbox to view the DCRs that are created.
You can see Mapping Summary, Job Information, and File Details on the page.
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:
Select on a job definition that failed with errors and select 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.
- Select Recurring Job Definition and specify the schedule
as required.Note: Scheduling isn’t 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.
- Select CONTINUE.On the Review page you can see the file details, mapping summary, and job information.
You can see the mapped required attributes count below the pie chart in the Mapping summary.
Edit the mapping or the record update preference if required by clicking Edit mapping and Edit job respectively.