Accelerate the Value of Data

Update Entity Attributes

Entity attribute values can change based on the values in the Update Date property and update Attribute Update Dates On Actual Changes flag.

The value of the updateAttributeUpdateDatesOnActualChanges flag is only considered when the POST {{api_uri}}/{{tenant}}/entities request does not contain the updateDate property.

The updateDate value of the entity and singleAttributesUpdateDates values of the entity attributes work together as described below.

Scenario 1: With Update Date

When the updateDate is available in the request query and updateAttributeUpdateDatesOnActualChanges flag is set to either true or false in the request body, the following sub-scenarios are possible:

Table 1. Entity's update date is available in the request
NumberSub-scenario'updateDate' and 'singleAttributesUpdateDates' values
1If no entity attributes are changed in the request body.The updateDate value in the response and singleAttributeUpdateDates values of the attributes do not change.
2If one or more entity attributes are changed and the other attributes are not available in the request body.
  • When 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:
    • If the updateDate specified in the request is earlier than the current updateDate , then the values of updateDate and singleAttributeUpdateDates attributes do not 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 does not change in the response but singleAttributeUpdateDates values for all attributes specified in the request body change to the updateDate value specified in the request.
3If one or more entity attributes are changed and all attributes are available in the request body.
  • The updateDate value in the response will be the same as the updateDate value in the request query.
  • Value of singleAttributeUpdateDates 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 do not change for the other attributes.
4If one or more entity attributes are changed and one or more attributes are not available in the request body.
  • The updateDate value in the response will be the same as the updateDate value in the request query.
  • If the new updateDate is later than or the same as the current updateDate, then the singleAttributeUpdateDates value of the changed attributes is the same as the updateDate specified in the request.
  • If the updateDate value in the request query is earlier than the current updateDate, then the singleAttributeUpdateDates value is set to empty for changed entity attributes.
  • The singleAttributesUpdateDates values do not change for the other attributes.

Scenario 2: Without Update Date

When the UpdateDate is not available in the request query and updateAttributeUpdateDatesOnActualChanges flag is set to either true or false in the request body, the following sub-scenarios are possible:

Table 2. Entity's update date is not available in the request
NumberSub-scenario'updateDate' and 'singleAttributesUpdateDates' values
1If 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.
2If one or more entity attributes are changed and the other attributes are not available 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.
3When the updateAttributeUpdateDatesOnActualChanges flag is set to false and if 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.
4When the updateAttributeUpdateDatesOnActualChanges flag is set to false and if 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.
5When the updateAttributeUpdateDatesOnActualChanges flag is set to true and if 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.
6When the updateAttributeUpdateDatesOnActualChanges flag is set to true and if 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.