Relationship not created due to endDate soft deletion logic
Learn why a relationship might not be created in Salesforce when an endDate is set in Reltio.
If a relationship exists in Reltio but isn't created or updated in Salesforce, it may be due to soft-deletion handling triggered by the endDate attribute. This behavior is designed to prevent synchronization of expired or logically inactive relationships.
Problem
- The relationship does not appear in Salesforce even though it exists in Reltio.
- No error appears in logs, but the event is skipped.
- A previously active relationship is no longer visible after
endDateis set.
Cause
The Salesforce Connector automatically skips relationship creation when the Reltio relation contains an endDate that is in the past or equal to the current date (based on UTC). This logic assumes the relationship is inactive and should not be created in Salesforce if it doesn't already exist.
Expected behavior
- New relationship with past endDate: Skipped entirely; no Salesforce record is created.
- Existing Salesforce record, and endDate updated to past: Salesforce is updated with
End_Date__c, and optionally updatesisInactive__c = true(if mapped/formula exists).
Log reference
Connector logs include the following line when skipping soft-deleted relationships:
Skipping relationship due to soft-deleted endDate
How to resolve or confirm
- Ensure the
endDatefield is included in your mapping if you're intentionally using soft-deletion logic. - If the relationship should still be created, remove or update the
endDateto a future value. - Optionally, map
isInactive__cas a formula field in Salesforce to reflect inactive status without removing the record.
endDate is mapped and present on the relation.