Reltio Create
Use Reltio Create for creating and writing data to Reltio objects.
Field Name | Description |
---|---|
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 Flow Based 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 & 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
|
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://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 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 |
It specifies number of records to be processed in a single API call. Default value: 50 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 create the Reltio Objects. 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 |
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 |
Determines the maximum number of attempts to get the response. Reltio uses the exponential backoff 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 Create operation.