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.
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.
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. |
|
3 | One or more entity attributes are changed and all attributes are included in the request body. |
|
4 | One or more entity attributes are changed and one or more attributes are not included in the request body. |
|
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.
Number | Sub-scenario | 'updateDate' and 'singleAttributesUpdateDates' values in response |
---|---|---|
1 | No entity attributes are changed in the request body. |
|
2 | One or more entity attributes are changed and the other attributes are not included in the request body. |
|
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. |
|
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. |
|
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. |
|
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. |
|