Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

 On this Page

Table of Contents
excludeOlder Versions|Additional Resources|Related Links|Related Information

Snap Type:Transform

 This Snap merges the Reltio Objects (Entities or Categories) data for a given Winner and Loser entity or for category IDs as mentioned on the Tenant. It provides a potential match between the two entities.  

Winner ID describes the Entity ID as a resulting 'survivor' and combines all attributes, crosswalks, roles and tags from the 'losing' entity into it.

Loser ID describes the Entity ID to be merged into the Winner (survivor) object, where an entity corresponds to one of the Reltio Objects.

ETL Transformations & Data Flow

The Snap transforms the existing entities provided as an input into a merged entity.

Input & Output

  • Input: The Input view is optional and is required only to pass the Winner/Loser ID from the upstream Snap or value in that field. Only the fields marked with an asterisk ( * ) are the required inputs; all other fields are optional.
  • OutputResponse for this Snap differs based on the operation selected. For potential matches, the Snap provides a 'success' or 'failure' message accordingly. For merging entities or categories, the Snap provides the attributes of the merged entity in the output.



A valid Reltio account with the tenant ID for the Tenant URL, or an  API key for the Account Settings to be generated.

The Reltio account must have sufficient access to merge the objects or entities from the Tenant.

Limitations and Known Issues:

None at this time.


Account & Access

This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See Reltio Account for information on setting up this type of account.

InputThis Snap has exactly one document input view.
OutputThis Snap has exactly one document output view.
ErrorThis Snap has at most one document error view and produces zero or more documents in the view.

Troubleshooting:None at this time.



Required. The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.

Tenant URL

Required. This determines the Reltio host with tenant ID. Use this format:


The value can be passed directly or through the pipeline parameters, but not through the upstream.


Default value: https://<your_reltio_host>/reltio/api/<tenant_id>


Specifies the merge operation to be performed. The available options are:

  • Merge Entities: Merges two entities.
  • Merge Categories: Merges two categories.
  • Potential Match For Entities: Provides a potential match for the entities.

Default valueMerge Entities

Winner Id

Required. Specifies the Winner entity or category identifier.

This field describes the entity ID as a resulting 'survivor' and combines all the attributes, crosswalks, roles and tags from the 'losing' entity into it.


The value can be passed using the upstream Snap or through the pipeline parameters.

Default value: $winnerId

Loser Id

Required. Specifies the loser entity or the category identifier. This field describes the Entity ID to be merged in the survivor object.


The value can be passed using the upstream Snap or through the pipeline parameters.

Default value: $loserId

Retry limit

Excerpt Include
Reltio Bulk Export
Reltio Bulk Export

Multiexcerpt include macro
nameSnap Execution
pageSOAP Execute

Multiexcerpt include macro
pageAnaplan Read

Basic Use Case

The following pipeline describes how the Snap functions as a standalone Snap in a pipeline:

Typical Snap Configurations

The key Snap configurations for the Snap are:

  • With Expressions
    The values are passes directly into the Snap:

  • Without Expressions
    • Using the Upstream Query: The values (Queue name and Queue URL) are passed using the upstream Snap:

  • Using the Pipeline Parameters: The values (Winner Id and Loser Id) are passed using the pipeline parameters:

The values set as the pipeline parameters:

Advanced Use Case

The following describes a pipeline, with a broader business logic involving multiple ETL transformations, that shows how typically in an enterprise environment, the Reltio functionality is used. The pipeline download is available in the Downloads section.

This pipeline retrieves the data from the Oracle Database and loads into the Reltio instance.

The key ETL transformations: 

Extract: The Oracle Select Snap retrieves the data from Oracle database.

Transform: The Head and the Mapper Snaps maps the specific data to be moved into the Reltio instance.

Load: The Reltio Create Snap creates the entities from the documents received from the upstream.

The pipeline further uses the Reltio Merge, Unmerge  and the Delete Snaps to perform the respective functions while transforming ( the JSON Splitter, Mapper and the Head Snaps) the data to serve the various business purposes.


patterns*slp, *zip

Excerpt Include
Reltio Snap Pack
Reltio Snap Pack