Reltio Integration Hub

Hi Everyone,

We have a scenario where we want to update one simple attribute to an existing entity in Reltio, But the crosswalk is something we are creating 

newly and not using an existing one. 

when checking the document, we used PreserveURI as an option during that Data load (preserveURIs Option | Reltio), because this allows us to insert 

an attribute to an existing account based on the URI and not the Crosswalk.

The API works fine while using PostMan, but when trying to use the RIH it creates a new account with the crosswalk value we provide.

PostMan : This one works and creates a new attribute with the crosswalk we provide, on an Existing entity ID that we pass in the URI

RIH API :

Notice that Entity URI is being passed as an attribute Value when trying to use RIH, Maybe this is the reason why it is creating a new entity instead 

of update the existing one. we are not able to find any other fields in RIH to pass the URI as a Value like how we used it in Postman.

------------------------------
Antony Anush
Qlik
------------------------------

Hi Antony,

Yes, the difference lies in the Entity URI as it is a attribute value instead of the base object.
Raise a Reltio request to enable the option like crosswalks/attributes and then you can map the value from previous step.

There is a workaround where you can use custom action from Reltio connector and have the json format as you had in Postman and you will get the right results.
Let me know if you need any help on Custom Action.

------------------------------
Sheshadri V
Fresh Gravity
------------------------------

Original Message:
Sent: 10-25-2022 02:43
From: Antony Anush
Subject: Reltio Integration Hub

Hi Everyone,

We have a scenario where we want to update one simple attribute to an existing entity in Reltio, But the crosswalk is something we are creating 

newly and not using an existing one. 

when checking the document, we used PreserveURI as an option during that Data load (preserveURIs Option | Reltio), because this allows us to insert 

an attribute to an existing account based on the URI and not the Crosswalk.

The API works fine while using PostMan, but when trying to use the RIH it creates a new account with the crosswalk value we provide.

PostMan : This one works and creates a new attribute with the crosswalk we provide, on an Existing entity ID that we pass in the URI

RIH API :

Notice that Entity URI is being passed as an attribute Value when trying to use RIH, Maybe this is the reason why it is creating a new entity instead 

of update the existing one. we are not able to find any other fields in RIH to pass the URI as a Value like how we used it in Postman.

------------------------------
Antony Anush
Qlik
------------------------------