Merging Using Reltio URIs

Using this API you can forcefully merge Salesforce Reltio Objects by providing a list of URIs.

The merge synchronization happens in sync mode, and the Reltio Objects will be added to the Salesforce Connector queue in due request runtime and will be processed in the future (when the connector processes this particular set of URIs).

Usage Scenarios

The following are some of the scenarios where the mergeByUris endpoint may be used:

To resolve inconsistency issues in case the merge has not been turned off for the corresponding entity type, but data has been already loaded to the tenant.
To retry merge in case the previous attempt has failed.

Request

POST: {SFDCConnectorUrl}/synchronization/{tenant}/{profile}/mergeByUris

Table 1. Parameters
Parameters	Name	Required	Description	Example
`Headers`	`Authorization`	true	Authorization header	`Barer {oauth_token}`
`Path`	`tenant`	true	Reltio tenant Id	SomeTenant
`Path`	`profile`	true	Profile Id	000000000000012345
`Body`		true	An array of entities or relations for corresponding object Type. Max size of all objects should not be greater than 1000.	`{ "configuration/entityTypes/HCP": [ "entities/eeeeee", "entities/cccccc" ], "configuration/entityTypes/Contact": [ "entities/rrrrrr", "entities/tttttt" ] }`

Response

The response is in JSON format with parameters.


Name	Description	Example
`reltioType`	Corresponding Reltio Object Type from Request	`configuration/entityTypes/Contact`
`{Reltio Object Id}` `/state` `/reason`	Reltio Object Id with state and reason for adding a particular Object to the synchronization queue	`"entities/rrrrrr": { "state": "failed", "reason": "Event: ENTITY_CHANGED -> entity entities/rrrrrr not found" }, "entities/eeeeee": { "state": "failed", "reason": "Already updated by sync user. Synchronization is not required" }`
`errors`	An array of error messages if an error occurred during an operation execution for the corresponding Reltio Type	`"errors": [ "No uri found for type: 'configuration/entityTypes/HCP1'." ]`

Possible Errors

The response is in JSON format with parameters.


Name	Description	Example
`400`	The tenant '${tenant}' or profile '${profile}' are not registered.	`Tenant` or `Profile` is not registered.
`400`	Incoming data should be valid JSON data.	Wrong `BODY` format - has to be valid JSON data.
`400`	Incoming data should be an Object.	Wrong `BODY` format - has to be Object.
`400`	Should be array data with size not more than 1000.	Number of all objects in the `BODY` should be lesser than `1000`.
`200`	Merge is switched off for Reltio type '${type}.	Merge is forbidden for this entity type. Turn on the merge in the mapping.
`200`	'${uri}' is not valid URI.	Invalid URI.
`200`	entity ${uri} not found.	The entity does not exist.
`200`	The entity is not suitable for sync. There are less than two active salesforce crosswalks.	The merge operation is not required for this entity as there is nothing to be merged.
`200`	Sync disabled for record{uri}.	The entity is filtered out. Verify the mapping filter for the corresponding type.

You've found your way to a temporary environment. Content is not complete or final. Looking for Reltio documentation? Go to docs.reltio.com.

© 2024 The RELTIO® mark is a registered trademark of Reltio, Inc. in the United States and other countries; DataDriven and Reltio Data Cloud are trademarks of Reltio, Inc. Other names or marks are trademarks of their respective owners.

Terms, Privacy Policy, and

Unify and manage your data

Merging Using Reltio URIs

Usage Scenarios

Response

Possible Errors

Footer