What is the singleAttributeUpdateDates section?

The singleAttributeUpdateDates section appears within each crosswalk in an entity’s JSON representation. It records timestamps for individual attributes, supporting recency-based survivorship by identifying the most recently updated values from contributing sources.

Why Salesforce updates might not be timestamped

When Reltio receives updates, not all modified attributes may appear in the singleAttributeUpdateDates section of the entity JSON. This occurs when:

• An attribute is excluded from the update request
• The attribute is included but its value hasn’t changed

Reltio timestamps only those attributes that are both included in the request and updated with a new value.

Default update behavior in Reltio

Reltio supports two update strategies for entity modifications: override and partialOverride.

By default, direct API requests to Reltio use the override strategy. In this mode, all included attributes overwrite existing values, and any attributes not present in the request are removed from the entity.

To preserve existing attributes and update only those explicitly provided, you can use the partialOverride strategy by including "partialOverride": true in the request payload.

Using partialOverride ensures that:

• Only attributes included and changed in the request are updated
• Attributes not included in the request remain unchanged
• Only modified attributes receive updated timestamps in the singleAttributeUpdateDates section of the entity JSON

This approach allows for flexible, targeted updates while maintaining efficient attribute-level tracking and accurate recency-based survivorship decisions.

How the Salesforce Connector applies updates

The Salesforce Connector adheres to this default partial update behavior. You do not need to explicitly configure partialOverride in your Connector mappings—it is always applied. The Salesforce Connector does not support partial updates to nested attributes. If a nested attribute is included in an update, it is treated as a whole object and replaced in full.

The enableNestedPartialOverride parameter is not supported in the Salesforce Connector and has no effect if defined in the tenant’s physical configuration.

Configuration options that affect timestamping

The following settings in your tenant’s configuration may influence whether Reltio records timestamps in the singleAttributeUpdateDates section:

• updateAttributeUpdateDates: Enables attribute-level timestamping
• updateDate: Overrides the update time with a custom timestamp
• updateAttributeUpdateDatesOnActualChanges: Suppresses timestamping unless the value changes

How to ensure accurate timestamp visibility

To ensure that attributes updated from Salesforce appear correctly in the entity JSON:

• Include all intended attributes in the update request
• Confirm that values differ from existing values
• Verify the relevant configuration flags are enabled, if applicable