The Salesforce connector has a designed behavior of Posting back to Reltio anytime it receives a Post from Reltio. As I discuss this further, consider another behavior it exhibits which is: When it Posts to Reltio, it does
not update the LUD of its crosswalk. It only updates the Reltio Load Date. Since the Recency rule ignores the Reltio Load Date, the Recency rule will not respect updates from Salesforce. If other systems are updating the LUD with their Posts, updates from Salesforce via the connector will
never win.
But here's the issue; even if the connector
did update the LUD of its crosswalk as it should, the loopback behavior would then become fundamentally problematic because the Post coming back from Salesforce will always carry a more recent timestamp (perhaps by just milliseconds) than the Post that went to Salesforce from Reltio. Therefore, with Recency as a strategy (which is quite common and popular), the Salesforce crosswalk will
always win regardless of which source system provided the most recent bonafide post. E.g. suppose you had 5 systems all Posting to Reltio each updating their crosswalk LUD. As long as the Salesforce connector is in the ecosystem, no other system can ever win via Recency because Salesforce's loopback feature will always come back milliseconds later with its own Post, thereby claiming victory from a recency standpoint.
I wonder if anyone else who has implemented the connector has encountered similar issues and has thoughts on this.
------------------------------
Curt Pearlman
PwC
Agoura Hills CA
------------------------------