In this article

Snap Type:Write
Description:

This Snap is used to un-merge the merged Reltio Objects (only Entities) on the mentioned Tenant. Based on Snap's configuration it is also possible to unmerge composite Entities. 

ETL Transformations & Data Flow

The Reltio Unmerge Snap transforms the merged Reltio Objects into separate un-merged entities.

Input & Output

  • Input: Input view is optional and is required only to pass the Origin Entity Id/ Spawn Entity Id from upstream Snaps or as a value in their corresponding properties.
  • Output: Response for the snap contains every field of each unmerged Entity.

Modes

Prerequisites:Reltio account with a valid Tenant Id so that Tenant URL can be formed/API for Account Settings. Also, the Reltio account must have write access in order to be able to create Objects in Tenant.
Limitations and Known Issues

You cannot roll back the productized Reltio Snap Pack in 4.20 to a prior version.

Configurations:

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.

Views

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 the moment.

Settings

Label

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. The format to be used is https://<reltio_host>/reltio/api/<tenant_id>. 

Example: https://sndbx.reltio.com/reltio/api/XK178mXYr3UZrG6/

Default value: https://test.reltio.com/reltiotest/api/XKiqdracb178fmuXYr3U7ZrG6/


This value can be provided dynamically as a pipeline parameter or directly in the Snap but not as an upstream parameter. 


Operations

This specifies the type of unmerge operation. Possible allowed values are Unmerge Entities and Not a potential match.

  • Unmerge Entities - This option performs unmerge of the provided Enitity object
  • Not a Potential Match - This option removes the “Potential Matches” option from those two entities. <need more info>

Default value: Unmerge Entities

Origin Entity Id

Required. This parameter describes the composite Entity Id which is the parent Entity ID (similar to Winner Id in Reltio Merge Snap) formed during the merge operation.

Default value: [None]


This value can be passed either as an upstream parameter or directly in the Snap but not as a pipeline parameter. 


Spawn Entity Id

Required. This parameter describes the Entity Id which is the child of the merged Entity (similar to Loser Id in Reltio Merge Snap) formed during the merge operation.

Default value: [None]


This value can be passed either as an upstream parameter or directly in the Snap but not as a pipeline parameter. 


Unmerge entity tree

This option can be used for a composite Entity, an Entity that is the result of several merge operations. If enabled, every component (contributor) can be unmerged to be a standalone entity again. If not selected, only the initial state of spawn without any merges would be unmerged.

Default value: Not selected

Retry limit


Examples

Basic Use Case

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

The Snap is configured with the following parameters:

An example of the output from executing this pipeline:

Typical Snap Configurations

Key configuration of the Snap lies in how the values are passed. The values can be passed:

  • Without Expression:

Values are passed directly into the Snap:

  • With Expression:
    • Using upstream parameters:

Values are passed as upstream 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.

Downloads