Unify and manage your data

Reltio Delete (By Object)

The following snaps are used to delete Reltio objects by object ID.

Table 1. Reltio Delete (By Object)
Field Name Description
Snap Type: Write
Description:

This Snap deletes Reltio objects (Entities/ Relations) from the mentioned Tenant. It also supports the Bulk operation by using the Bulk Delete functionality. This Snap cannot be used for deleting Interactions because transaction-based data cannot be deleted.

ETL Transformations & Data Flow

The Reltio Delete (Object) Snap extracts (or deletes) the corresponding data from the Reltio Tenant.

Input & Output

  • Input: Input view is optional and is required only to pass the Object ID from the upstream Snap or value in that field.
  • Output: Response for the Snap contains either success or an error, depending on whether the URI was deleted or not.

Modes

  • Ultra pipelines: May work in Ultra Pipelines.
  • Spark (Deprecated) mode: Not supported in Spark mode.
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 to delete objects in the Tenant.

Limitations and Known Issues None at the moment.
Configurations:

Account & Access

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

Views

Input
This Snap has at most one document input view.
Output
This Snap has exactly one document output view.
Error
This Snap has at most one document error view and produces zero or more documents in the view.
Troubleshooting: The section describes typical issues you may encounter while using this Snap, and instructions on how to workaround them:
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. Use this format:

https://<reltio_host>/api/tenant_id>.

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

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

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

Object

Required.

The Reltio Object to be created. This is a suggestible field.

Reltio typically has 3 objects - Entities/ Interactions/Relations. Suggestion only works if the valid account/ tenant URL is provided.

Default value: [None]

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

Object Id

Required.

Describes the part of the “URI” in the Reltio API response. For example: “uri”: “entities/abcd1234” is a part of a Reltio Entity object, so abcd1234 is the Object Entity ID. In the Reltio UI,“Entity ID” is in the profile of each Entity Object.

Default value: [None]

Bulk delete

Supports deleting multiple entities at a time; accepts a comma-separated list of entities.

Default value: Not selected

Retry limit

The maximum number of times the Snap will attempt to get the response. Reltio uses the exponential back off retry policy only for HTTP Status Codes 502, 503 and 504. Reltio has no retry policy for HTTP Status Codes 401, 403, 404, 500.

Default value: 5

Maximum value: 10

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

Execute during preview

Executes the Snap during a pipeline Save operation so that the output view can produce the preview data.

Default value: Not selected

See the below examples for the basic and advanced use case and typical Snap configurations for the Delete (By Object) operation.