Reltio to Salesforce

User performs one of the following actions: Creates, updates, deletes or merges entities:

• Creates, updates, deletes or merges entities

• Creates, updates or deletes relationships between entities

Platform sends the event to an external queue (AWS SQS). Each event contains the URI of the changed entity/entities and user who did the data change.

• The connector ignores such an event or moves this event from the external queue to the connector queue to process it, if the user is service user.
• For creates and updates, you can configure the Salesforce connector to filter out events based on what is updated in Reltio. If, in Reltio, there are only changes to attribute values that are not part of the connector mappings, then the connector ignores the event and does not trigger the integration. Note that this filtering capability is only available for Reltio to Salesforce data sync process. See the parameter deltaFiltering in topic Configure your Salesforce Connector Profile.
• Reltio Integration for Salesforce supports the DELETE operation for Reltio's reference attributes mapped to custom Salesforce objects and account embedded address. Enable the DELETE operation, add "deltaFiltering": true to the Reltio profile configuration in the "reltio" section and "deleteRelatedObjects": true in the entity mapping to ensure that a delta is present in SQS events.

  Note:

  • When an attribute is removed from the Reltio UI, only the Reltio value is removed. Other values from different crosswalks are marked as ignored and become OV false. All address field values in the account are also removed.
  • If all attribute values are removed from the entity, all address field values in the account are removed.
• The connector gets the entity(ies) values from Reltio.
• The entity is converted to a Salesforce Object (sobject) according to the mapping rules.
• The Salesforce connector makes API calls to Create/Update/Delete objects in Salesforce.
• The connector executes a callback request, if the API call is successful, and puts all data that was sent to Salesforce under the Salesforce crosswalk and the event is removed from the queue.
• A retry mechanism is initiated if the API call to Salesforce fails.
  Note: A retry mechanism has been added so that tasks can execute successfully if a subsequent retry is successful.

  • The default retries count for all requests to Reltio is 4. The retry count can be configured in profile configuration by using the maxRetries parameter.
  • The default retry interval is one second. The retry interval can be configured in profile configuration by using the delayBetweenRetries parameter.

Salesforce to Reltio