Unwanted timestamp updates on unchanged attributes
Learn about why attributes in Salesforce may be updated with new timestamps even when values haven't changed in Reltio.
In some cases, attributes in Salesforce may appear as newly updated, even when their values haven’t changed in Reltio. This happens when the connector resends the full attribute set during update events, including values that remain the same. The result is an unintended refresh of timestamps, especially Last Update Date (LUD), which may affect survivorship rules or downstream integrations.
Problem
- Attributes like
EmailorPhoneappear in Salesforce with refreshed timestamps. - Survivorship in Reltio flips unexpectedly after syncs.
- Audit logs show an update was pushed, but the values did not change.
Cause
By default, the Salesforce Connector includes all mapped attributes in update payloads. Even if a value hasn't changed, including the field in the payload may trigger a timestamp refresh in Salesforce.
Resolution
To avoid this behavior, enable the skipUnchangedAttributes flag in the connector profile configuration. When set to true, only changed attributes are included in the outbound update payload.
Add the following to your profile's block:
"skipUnchangedAttributes": true
This setting ensures that unchanged values are omitted from update events, preventing LUD refresh and stabilizing survivorship based on update timestamps.
Example behavior
With skipUnchangedAttributes enabled:
- Only fields that have changed values are included in the update payload.
- Nested attributes (like
Email) only trigger updates if one of their values actually changes. - Connector logs may show smaller payloads or reduced update activity.