On this Page
| Snap Type: | Write | ||||||
|---|---|---|---|---|---|---|---|
| Description: | This Snap creates and writes data to the Reltio objects (Entities/ Relations/ Interactions/ Categories) in a Reltio instance. To configure this Snap, you must specify the type of object to create, the Tenant URL, and so on. You can also configure query parameters and their corresponding values. ETL Transformations & Data FlowBased on the Snap configuration, the Reltio Create Snap performs a load operation by writing into the Reltio instance. 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 write access to create objects in the Tenant. | ||||||
| Limitations and Known Issues | None. | ||||||
| Configurations: | Account & AccessThis 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
| ||||||
| 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. Use this format: https://<reltio_host>/reltio/api/<tenant_id>. Example: https://test.reltio.com/reltiotest/api/XKiqdracb178fmuXYr3U7ZrG6/ 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 4 objects - Entities/ Interactions/ Relations/ Categories. Suggestion only works if a 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 types | Required. Based on the Object selected, this property can be configured to select the object type. This is a suggestible field, but the suggestion works only if a valid account/ tenant URL/ object 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. | ||||||
| Batch size | Specifies the number of records that you want the Snap to process in a single API call. Default value: 1 Minimum value: 1 Maximum value: 2,147,483,647 This value can be provided dynamically as a pipeline parameter or directly in the Snap, but not as an upstream parameter. | ||||||
| Thread limit | Required. Specifies the maximum threads of this Snap to delete the Reltio Objects. Minimum value: 1 Maximum value: 50 Default value: 20 This value can be provided dynamically as a pipeline parameter or directly in the Snap, but not as an upstream parameter. | ||||||
| Query parameters | Defines the query parameters and their values. The query parameters will be attached to the URL using the HTTP query parameter syntax, separated by & added as key=value. | ||||||
| Query parameter | Key which can be used in the HTTP request for Reltio. Default value: [None] This value can be provided dynamically as a pipeline parameter or directly in the Snap, but not as an upstream parameter. | ||||||
| Query parameter value | Value associated with the specified Query parameter key. Default value: [None] This value can be provided dynamically as a pipeline parameter or directly in the Snap, but not as an upstream parameter. | ||||||
| Retry limit | Specify the maximum number of attempts to get the response. Minimum value: 1 Default Value: 5 You can provide this value dynamically as a Pipeline parameter or directly in the Snap, but not as an upstream value. | ||||||
Snap execution | Select one of the three modes in which the Snap executes. Available options are:
| ||||||
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 data from executing this pipeline:
Exported pipeline is available in the Downloads section below.
Typical Snap Configurations
Key configuration of the Snap lies in how the values are passed. The values can be passed:
- Without Expressions:
Values are passed directly in the Snap:
- With Expressions:
- Using 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
