Retrieve or modify an entity crosswalk updateDate

Learn how to update the values of entity attributes using the Entity API.

It's important to determine which source system has the most recent information about the data for the purposes of recency for OV rules. Reltio determines the last update date, that is the date a crosswalk record was updated in the source system, using the updateDate system data attribute. If you don't specify the updateDate parameter when you update an entity, both the create and update dates for the crosswalk will be the same, so OV recency rules can't determe which attribute from a collection is the most recent. For more information, see topic Managing Crosswalk Dates.

Manage the value in updateDate crosswalk attribute for partial overrides with these options in the Entities: singleAttributesUpdateDates and updateAttributeUpdateDatesOnActualChanges. For more information, see topic Update entities.

Note:

The Entities considers the value of the updateAttributeUpdateDatesOnActualChanges option only if you don't include the updateDate attribute in the request.

Scenario 1: Update entity attributes with update dates

These scenarios explain the responses for entity attributes with updated dates, depending on the parameters you specify in your Entities update request.

Table 1. Responses for entity attributes with updated dates
Number	Sub-scenario	'updateDate' and 'singleAttributesUpdateDates' values in response
1	No entity attributes are changed in the request body.	The updateDate value in the response and singleAttributeUpdateDates values of the attributes don't change.
2	One or more entity attributes are changed and the other attributes are not included in the request body.	When the request contains the partialOverride option, the values of updateDate and singleAttributeUpdateDates attributes don't change in the response. When the request contains both the partialOverride and updateAttributeUpdateDates: If the updateDate specified in the request is earlier than the current updateDate value, then the values of updateDate and singleAttributeUpdateDates attributes don't change in the response. If the updateDate specified in the request is later than or the same as the current updateDate value, then the updateDate value doesn't change in the response but singleAttributeUpdateDates values for all attributes specified in the request body change to the updateDate value specified in the request.
3	One or more entity attributes are changed and all attributes are included in the request body.	The updateDate value in the response will be the same as the updateDate value in the request query. The singleAttributeUpdateDates value will be set to `empty` for all changed entity attributes and attributes that have a singleAttributeUpdateDates value earlier than the updateDate specified in the request. The singleAttributesUpdateDates values don't change for the other attributes.
4	One or more entity attributes are changed and one or more attributes are not included in the request body.	The updateDate value in the response doesn't change. If the new updateDate is later than or the same as the current updateDatevalue, then the singleAttributeUpdateDates value of the changed attributes is the same as the updateDate value specified in the request. If the updateDate value in the request is earlier than the current updateDate value, then the singleAttributeUpdateDates value is set to `empty` for changed entity attributes. The singleAttributesUpdateDates values don't change for the other attributes.

Scenario 2: Update entity attributes without update dates

These scenarios explain the responses for entity attributes without updated dates, depending on the parameters you specify in your Entities update request.

Table 2. Responses for entity attributes without updated dates
Number	Sub-scenario	'updateDate' and 'singleAttributesUpdateDates' values in response
1	No entity attributes are changed in the request body.	When only the partialOverride option is used in the request query, the values of updateDate and singleAttributeUpdateDates attributes do not change in the response. When both the partialOverride and updateAttributeUpdateDates options are used in the request query, the values of updateDate and singleAttributeUpdateDates attributes do not change in the response.
2	One or more entity attributes are changed and the other attributes are not included in the request body.	When only the partialOverride option is used in the request query, the value of the updateDate attribute does not change and singleAttributeUpdateDates attribute is changed to the current date and time in the response. The singleAttributesUpdateDates values do not change for the other attributes. When both the partialOverride and updateAttributeUpdateDates options are used in the request query, the value of the updateDate attribute does not change and singleAttributeUpdateDates attribute is changed to the current date and time in the response. The singleAttributesUpdateDates values do not change for the other attributes.
3	The updateAttributeUpdateDatesOnActualChanges flag is set to `false`, all attributes within a crosswalk are in the request payload, and one or more attributes are changed.	When only the partialOverride option is used in the request query, the value of the updateDate attribute does not change, the singleAttributeUpdateDates for the changed attributes are made blank in the request body, and the singleAttributeUpdateDates for the other attributes do not change in the response. When both the partialOverride and updateAttributeUpdateDates options are used in the request query, the value of the updateDate attribute does not change and all attributes in the singleAttributeUpdateDates section in the request body are changed to the current date and time in the response.
4	The updateAttributeUpdateDatesOnActualChanges flag is set to `false`, some attributes within a crosswalk are in the request payload, and one or more attributes are changed.	When only the partialOverride option is used in the request query, the value of the updateDate attribute does not change and all attributes in the singleAttributeUpdateDates section in the request body are changed to the current date and time in the response. When both the partialOverride and updateAttributeUpdateDates options are used in the request query, the value of the updateDate attribute does not change and all attributes in the singleAttributeUpdateDates section in the request body are changed to the current date and time in the response.
5	The updateAttributeUpdateDatesOnActualChanges flag is set to `true`, all attributes within a crosswalk are in the request payload, and one or more attributes are changed.	When only the partialOverride option is used in the request query, the value of the updateDate attribute does not change, the singleAttributeUpdateDates for the changed attributes are made blank in the request body, and the singleAttributeUpdateDates for the other attributes do not change in the response. When both the partialOverride and updateAttributeUpdateDates options are used in the request query, the value of the updateDate attribute does not change, the singleAttributeUpdateDates for the changed attributes are changed to the current date and time, and the singleAttributeUpdateDates for the other attributes do not change in the response.
6	The updateAttributeUpdateDatesOnActualChanges flag is set to `true`, some attributes within a crosswalk are in the request payload, and one or more attributes are changed.	When only the partialOverride option is used in the request query, the value of the updateDate attribute does not change, the singleAttributeUpdateDates for the changed attributes are changed to the current date and time, and the singleAttributeUpdateDates for the other attributes do not change in the response. When both the partialOverride and updateAttributeUpdateDates options are used in the request query, the value of the updateDate attribute does not change, the singleAttributeUpdateDates for the changed attributes are changed to the current date and time, and the singleAttributeUpdateDates for the other attributes do not change in the response.

Unify and manage your data

Retrieve or modify an entity crosswalk updateDate

Scenario 1: Update entity attributes with update dates

Scenario 2: Update entity attributes without update dates

Footer