Reltio Connect

Hello Reltio Community,

I'm looking for guidance on a crosswalk conflict scenario we're encountering and would appreciate input on the recommended product-level approach.

Scenario

In the source system, a customer record is initially created as a Person with a static source key (for example, 123). At a later point, that same record is converted to an Organization, while retaining the same source key.
At any given time, only one record exists in the source - it is updated in place rather than creating a new record.

The crosswalk source and source key therefore remain unchanged across the conversion.

Observed behavior in Reltio

• When the record is converted from Person to Organization in the source and we attempt to load the Organization into Reltio, the load is rejected because the crosswalk already exists under the Person entity.

• We attempted to soft delete the Person entity and then load the Organization, but the load still fails with the same crosswalk conflict.

• The only approach that has worked so far is to hard delete the Person entity first and then load the Organization, after which the Organization is created successfully with the same crosswalk.

Questions

1. Is there a recommended or supported way in Reltio to handle Person ↔ Organization conversions with a static crosswalk without requiring a hard delete of the existing entity?

2. Using the Reltio Data Loader, is it correct that hard deletes are not supported?

3. We are automating our loads using Reltio Integration Hub (RIH). If hard delete is the only viable approach, we are considering performing the delete using the Delete API prior to loading the converted record.

   • Are there best practices or design considerations for handling this pattern via API?

   • Has anyone implemented a similar approach successfully?

We're trying to align our implementation with recommended product patterns, so any guidance or insights would be greatly appreciated.

Thank you,
Rushy

Hi Rushy,

If you know the trigger when an entity converts from a person to organization (or vice versa), you can use the API below to change the type:

Hello Reltio Community,

I'm looking for guidance on a crosswalk conflict scenario we're encountering and would appreciate input on the recommended product-level approach.

Scenario

In the source system, a customer record is initially created as a Person with a static source key (for example, 123). At a later point, that same record is converted to an Organization, while retaining the same source key.
At any given time, only one record exists in the source - it is updated in place rather than creating a new record.

The crosswalk source and source key therefore remain unchanged across the conversion.

Observed behavior in Reltio

• When the record is converted from Person to Organization in the source and we attempt to load the Organization into Reltio, the load is rejected because the crosswalk already exists under the Person entity.

• We attempted to soft delete the Person entity and then load the Organization, but the load still fails with the same crosswalk conflict.

• The only approach that has worked so far is to hard delete the Person entity first and then load the Organization, after which the Organization is created successfully with the same crosswalk.

Questions

1. Is there a recommended or supported way in Reltio to handle Person ↔ Organization conversions with a static crosswalk without requiring a hard delete of the existing entity?

2. Using the Reltio Data Loader, is it correct that hard deletes are not supported?

3. We are automating our loads using Reltio Integration Hub (RIH). If hard delete is the only viable approach, we are considering performing the delete using the Delete API prior to loading the converted record.

   • Are there best practices or design considerations for handling this pattern via API?

   • Has anyone implemented a similar approach successfully?

We're trying to align our implementation with recommended product patterns, so any guidance or insights would be greatly appreciated.

Thank you,
Rushy

Hi Snehil,

Thank you for your response? Whats the API to use? 

Currently we have only batch integration enabled? is there a way this can be done without API call?

Regards,

Rushy A

Hi Rushy,

If you know the trigger when an entity converts from a person to organization (or vice versa), you can use the API below to change the type:

Hello Reltio Community,

I'm looking for guidance on a crosswalk conflict scenario we're encountering and would appreciate input on the recommended product-level approach.

Scenario

In the source system, a customer record is initially created as a Person with a static source key (for example, 123). At a later point, that same record is converted to an Organization, while retaining the same source key.
At any given time, only one record exists in the source - it is updated in place rather than creating a new record.

The crosswalk source and source key therefore remain unchanged across the conversion.

Observed behavior in Reltio

• When the record is converted from Person to Organization in the source and we attempt to load the Organization into Reltio, the load is rejected because the crosswalk already exists under the Person entity.

• We attempted to soft delete the Person entity and then load the Organization, but the load still fails with the same crosswalk conflict.

• The only approach that has worked so far is to hard delete the Person entity first and then load the Organization, after which the Organization is created successfully with the same crosswalk.

Questions

1. Is there a recommended or supported way in Reltio to handle Person ↔ Organization conversions with a static crosswalk without requiring a hard delete of the existing entity?

2. Using the Reltio Data Loader, is it correct that hard deletes are not supported?

3. We are automating our loads using Reltio Integration Hub (RIH). If hard delete is the only viable approach, we are considering performing the delete using the Delete API prior to loading the converted record.

   • Are there best practices or design considerations for handling this pattern via API?

   • Has anyone implemented a similar approach successfully?

We're trying to align our implementation with recommended product patterns, so any guidance or insights would be greatly appreciated.

Thank you,
Rushy