Reltio Connect

Hi Team,

I hope this message finds you well. We are currently working on integrating organizational data into Reltio from multiple sources and enriching this data using the Reltio D&B connector. During this process, hierarchies and relationships are typically formed, presenting a unique challenge based on our project requirements.

Use Case Overview: Our client has specified that we should avoid creating any parent/child hierarchy within Reltio. The reason being, such a hierarchy automatically generates corresponding parent/child profiles within the tenant, which is restricted in this project. However, the client still requires hierarchical data to be stored in Reltio, but without generating these profiles. After discussing with Reltio, it was suggested that we could use either nested attributes or reference attributes to fulfill this requirement. Specifically, using a reference entity was recommended for ease of management and updating (e.g., changing "Walmart" to "Walmart Corp" in one place affects all 20 records).

Inquiries and Requests for Guidance:

1. Verification of Understanding: Could you please confirm our understanding that the Reltio native connectors, such as the D&B connector's getMatch and getCompanyDetails APIs, are capable of storing data as nested attributes within the Reltio MDM Entity?

2. Inquiry on Hierarchical Information Storage: Is there any Reltio native connector that supports the storage of hierarchy information specifically as a reference attribute? This feature would greatly simplify our current challenge.

3. Implementation Guidance: We are seeking further guidance on the optimal implementation of this solution using reference attributes to manage hierarchical data without creating new profiles. Could you provide us with detailed best practices, procedural steps, or strategic advice to effectively achieve this?

Your expertise and insights into these matters would be invaluable as we aim to navigate these requirements efficiently and effectively. We appreciate your support and look forward to your prompt response.

------------------------------
Avni Kanchan
Deloitte
------------------------------

Hi Team,

I hope this message finds you well. We are currently working on integrating organizational data into Reltio from multiple sources and enriching this data using the Reltio D&B connector. During this process, hierarchies and relationships are typically formed, presenting a unique challenge based on our project requirements.

Use Case Overview: Our client has specified that we should avoid creating any parent/child hierarchy within Reltio. The reason being, such a hierarchy automatically generates corresponding parent/child profiles within the tenant, which is restricted in this project. However, the client still requires hierarchical data to be stored in Reltio, but without generating these profiles. After discussing with Reltio, it was suggested that we could use either nested attributes or reference attributes to fulfill this requirement. Specifically, using a reference entity was recommended for ease of management and updating (e.g., changing "Walmart" to "Walmart Corp" in one place affects all 20 records).

Inquiries and Requests for Guidance:

1. Verification of Understanding: Could you please confirm our understanding that the Reltio native connectors, such as the D&B connector's getMatch and getCompanyDetails APIs, are capable of storing data as nested attributes within the Reltio MDM Entity?

2. Inquiry on Hierarchical Information Storage: Is there any Reltio native connector that supports the storage of hierarchy information specifically as a reference attribute? This feature would greatly simplify our current challenge.

3. Implementation Guidance: We are seeking further guidance on the optimal implementation of this solution using reference attributes to manage hierarchical data without creating new profiles. Could you provide us with detailed best practices, procedural steps, or strategic advice to effectively achieve this?

Your expertise and insights into these matters would be invaluable as we aim to navigate these requirements efficiently and effectively. We appreciate your support and look forward to your prompt response.

Hi Avni,

To clarify the ask, the GetCompanyDetails call returns hierarchy attributes like Parent/HQ, name, address, and DUNS Number.  The Reltio application then automatically creates a profile for the Parent/HQ in MDM and creates the Parent/Child relationship between the 2 profiles.  Your ask is to disable the creation of the profile for the Parent/HQ and instead, store this information as attributes on the profile that has been enriched.  Is this correct?

@Gaurav Gera Can Reltio create fields on the profile for the D&B Linkage information?  And can the Profile Creation process be disabled within the D&B Connector?  Adding the fields should allow the customer to create reports on hierarchies (all records with a Global Ultimate DUNS Number = to xxxxxxxxx) without actually creating the hierarchy in Reltio.

Hi Team,

I hope this message finds you well. We are currently working on integrating organizational data into Reltio from multiple sources and enriching this data using the Reltio D&B connector. During this process, hierarchies and relationships are typically formed, presenting a unique challenge based on our project requirements.

Use Case Overview: Our client has specified that we should avoid creating any parent/child hierarchy within Reltio. The reason being, such a hierarchy automatically generates corresponding parent/child profiles within the tenant, which is restricted in this project. However, the client still requires hierarchical data to be stored in Reltio, but without generating these profiles. After discussing with Reltio, it was suggested that we could use either nested attributes or reference attributes to fulfill this requirement. Specifically, using a reference entity was recommended for ease of management and updating (e.g., changing "Walmart" to "Walmart Corp" in one place affects all 20 records).

Inquiries and Requests for Guidance:

1. Verification of Understanding: Could you please confirm our understanding that the Reltio native connectors, such as the D&B connector's getMatch and getCompanyDetails APIs, are capable of storing data as nested attributes within the Reltio MDM Entity?

2. Inquiry on Hierarchical Information Storage: Is there any Reltio native connector that supports the storage of hierarchy information specifically as a reference attribute? This feature would greatly simplify our current challenge.

3. Implementation Guidance: We are seeking further guidance on the optimal implementation of this solution using reference attributes to manage hierarchical data without creating new profiles. Could you provide us with detailed best practices, procedural steps, or strategic advice to effectively achieve this?

Your expertise and insights into these matters would be invaluable as we aim to navigate these requirements efficiently and effectively. We appreciate your support and look forward to your prompt response.

Hi Avni,

To clarify the ask, the GetCompanyDetails call returns hierarchy attributes like Parent/HQ, name, address, and DUNS Number.  The Reltio application then automatically creates a profile for the Parent/HQ in MDM and creates the Parent/Child relationship between the 2 profiles.  Your ask is to disable the creation of the profile for the Parent/HQ and instead, store this information as attributes on the profile that has been enriched.  Is this correct?

@Gaurav Gera Can Reltio create fields on the profile for the D&B Linkage information?  And can the Profile Creation process be disabled within the D&B Connector?  Adding the fields should allow the customer to create reports on hierarchies (all records with a Global Ultimate DUNS Number = to xxxxxxxxx) without actually creating the hierarchy in Reltio.

Hi Team,

I hope this message finds you well. We are currently working on integrating organizational data into Reltio from multiple sources and enriching this data using the Reltio D&B connector. During this process, hierarchies and relationships are typically formed, presenting a unique challenge based on our project requirements.

Use Case Overview: Our client has specified that we should avoid creating any parent/child hierarchy within Reltio. The reason being, such a hierarchy automatically generates corresponding parent/child profiles within the tenant, which is restricted in this project. However, the client still requires hierarchical data to be stored in Reltio, but without generating these profiles. After discussing with Reltio, it was suggested that we could use either nested attributes or reference attributes to fulfill this requirement. Specifically, using a reference entity was recommended for ease of management and updating (e.g., changing "Walmart" to "Walmart Corp" in one place affects all 20 records).

Inquiries and Requests for Guidance:

1. Verification of Understanding: Could you please confirm our understanding that the Reltio native connectors, such as the D&B connector's getMatch and getCompanyDetails APIs, are capable of storing data as nested attributes within the Reltio MDM Entity?

2. Inquiry on Hierarchical Information Storage: Is there any Reltio native connector that supports the storage of hierarchy information specifically as a reference attribute? This feature would greatly simplify our current challenge.

3. Implementation Guidance: We are seeking further guidance on the optimal implementation of this solution using reference attributes to manage hierarchical data without creating new profiles. Could you provide us with detailed best practices, procedural steps, or strategic advice to effectively achieve this?

Your expertise and insights into these matters would be invaluable as we aim to navigate these requirements efficiently and effectively. We appreciate your support and look forward to your prompt response.

Hi @Jay Daly

Within the Reltio profile that is enriched as shown below in the screenshot. I have also answered rest of the question the thread I shared in the previous response.

Hi Avni,

To clarify the ask, the GetCompanyDetails call returns hierarchy attributes like Parent/HQ, name, address, and DUNS Number.  The Reltio application then automatically creates a profile for the Parent/HQ in MDM and creates the Parent/Child relationship between the 2 profiles.  Your ask is to disable the creation of the profile for the Parent/HQ and instead, store this information as attributes on the profile that has been enriched.  Is this correct?

@Gaurav Gera Can Reltio create fields on the profile for the D&B Linkage information?  And can the Profile Creation process be disabled within the D&B Connector?  Adding the fields should allow the customer to create reports on hierarchies (all records with a Global Ultimate DUNS Number = to xxxxxxxxx) without actually creating the hierarchy in Reltio.

Hi Team,

I hope this message finds you well. We are currently working on integrating organizational data into Reltio from multiple sources and enriching this data using the Reltio D&B connector. During this process, hierarchies and relationships are typically formed, presenting a unique challenge based on our project requirements.

Use Case Overview: Our client has specified that we should avoid creating any parent/child hierarchy within Reltio. The reason being, such a hierarchy automatically generates corresponding parent/child profiles within the tenant, which is restricted in this project. However, the client still requires hierarchical data to be stored in Reltio, but without generating these profiles. After discussing with Reltio, it was suggested that we could use either nested attributes or reference attributes to fulfill this requirement. Specifically, using a reference entity was recommended for ease of management and updating (e.g., changing "Walmart" to "Walmart Corp" in one place affects all 20 records).

Inquiries and Requests for Guidance:

1. Verification of Understanding: Could you please confirm our understanding that the Reltio native connectors, such as the D&B connector's getMatch and getCompanyDetails APIs, are capable of storing data as nested attributes within the Reltio MDM Entity?

2. Inquiry on Hierarchical Information Storage: Is there any Reltio native connector that supports the storage of hierarchy information specifically as a reference attribute? This feature would greatly simplify our current challenge.

3. Implementation Guidance: We are seeking further guidance on the optimal implementation of this solution using reference attributes to manage hierarchical data without creating new profiles. Could you provide us with detailed best practices, procedural steps, or strategic advice to effectively achieve this?

Your expertise and insights into these matters would be invaluable as we aim to navigate these requirements efficiently and effectively. We appreciate your support and look forward to your prompt response.