On this Page
| Table of Contents | ||||
|---|---|---|---|---|
|
| Snap Type: | Write | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description: | This Snap is used to delete records associated with the Reltio Objects (Entities/ Relations/ Categories) from the mentioned Tenant based on the URI configured. It also supports the bulk operation by using Bulk Delete functionality. The Reltio Delete (URI) Snap cannot be used for deleting Interactions since they are transaction based data and cannot be deleted. ETL Transformations and Data FlowThe Reltio Delete (URI) Snap extract's (or deletes) the corresponding data from the Reltio tenant. Input & Output
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 sufficient access in order to be able to delete 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 & AccessThis 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
| ||||||||||||
| 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>/api/tenant_id>. Example: https://test.reltio.com/reltiotest/api/XKiqdracb178fmuXYr3U7ZrG6/ Default value: https://<your_reltio_host>/reltio/api/<tenant_id>
| ||||||||||||
| URI | Required. This describes the actual Object which needs to be deleted based on the URI parameter. For example: “uri”: “entities/abcd1234” is a part of Reltio object (Entity here). Also if the Bulk delete property is enabled, then multiple entities' URIs can be provided separated by commas. Default value: [None] | ||||||||||||
| Bulk delete | This property enables deleting multiple Entities at a time. Default value: Not selected | ||||||||||||
| Retry limit |
| ||||||||||||
| Batch size |
| ||||||||||||
| Thread 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 pipeline parameters:
Values are passed as 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.
Downloads
| Multiexcerpt include macro | ||||
|---|---|---|---|---|
|
| Attachments | ||
|---|---|---|
|
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|