Reltio Read (Crosswalk)

Read

This Snap reads Reltio entities from a specified Tenant. For information on using Reltio objects other than entities (interactions, relations, and categories,) see Reltio Read (Object).

ETL Transformations and Data Flow

This Snap reads data from the Reltio Object and Object Type.

Input & Output

• Input: 
  There should be one input view to provide the Object type or the values which are also suggested in the Input Schema. The fields marked in (*) only are the required inputs. Others are optional.

• Output:
  Response contains the attribute values for each entity object (separate record for each input entity) provided.

Modes

• Ultra Pipelines: Works in Ultra Pipelines.

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

Access in Reltio to read objects and entities from the Tenant.

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

Account and Access

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

Views

 None at this time.

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

Required. Specifies the Reltio host with Tenant ID. The format used is https://<reltio_host>/reltio/api/<tenant_id>.  

The values can be passed directly or using the pipeline parameters but not through the upstream.

Example: https://test.reltio.com/reltiotest/api/XKiqdracb178fmuXYr3U7ZrG6/

Default value: [None]

Required. The Reltio Object to be created. You can either enter a valid object name or select an object from the suggestions displayed. 

Reltio typically has four objects:

• entities: Entities are objects for the representation.

• categories: Entities are structured under the Categories. An entity can belong to multiple categories.

• interactions: Interactions are the actions between two or more entities that have an impact on one another. For example: email is an interaction that sends emails to one one or several entities. One can also define different types of interactions in their instance depending on the business model.

• relations: Define the links between entities.

The suggestion works only when the valid account or the Tenant URL is provided.

The values can be passed directly or using the pipeline parameters.

Default value: [None]

Specify query parameters and their values. Use the http query parameter syntax to attach query parameters to the URL, separating each parameter using an '&'.

Specify the key to be used in the HTTP request for Reltio.

 Default value: [None]

It is the key value for the particular Query parameter used.

Default value: [None]

This value indicates whether or not to nest the values of same attributes. If not selected, then an attribute having multiple values will be shown in two different tags else it will be grouped in a single tag.

Default value: Not selected

Select one of the following three modes in which the Snap executes:

• Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.

• Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.

• Disabled: Disables the Snap and all Snaps that are downstream from it.

Default Value: Execute only
Example: Validate & Execute