Reltio Connect

Hi Team,

Can you please help us with the resolution of the below usecase.

Use Case : We are loading Organization data in Reltio from multiple sources and we are also enriching that data using Reltio D&B connector. We can create Hierarchies and Relationships during the enrichment process and it will create the upward family linkage which can be optionally brought in, constructed automatically during the account enrichment process, and visualized as a parent/child hierarchy. In our project the specific ask from the client is to not create any parent/child hierarchy because if we create parent child hierarchy then the corresponding parent/child profiles will get created in the tenant which is restricted here but we need to store the hierarchical data in Reltio (without creating profile). So to achieve this requirement we can store this hierarchical information either in Nested attributes or reference Attributes. In a small discussion with Reltio we got the suggestion If we create reference entity it would be easy to master and update in 1 place. Example we get Walmart as global parent for 20 records, storing as reference entity will help us to modify Walmart to Walmart Corp at only 1 place

• Ask 1: Verification of Understanding: Please validate our understanding that the native connectors, such as the Reltio D&B connector (getMatch and getCompanyDetails api), will be able to store data in Reltio MDM Entity as nested attributes.
• Ask 2: Inquiry on Hierarchical Information Storage: We would like to know if there is any Reltio native connector available that stores Hierarchy information as a reference attribute.
• Ask 3: Implementation Guidance: We seek Reltio's additional guidance on how to best implement this solution using a reference attribute to avoid the creation of new profiles. Could you provide us with best practices, steps, or strategies to achieve this?

Hi Team,

Can you please help us with the resolution of the below usecase.

Use Case : We are loading Organization data in Reltio from multiple sources and we are also enriching that data using Reltio D&B connector. We can create Hierarchies and Relationships during the enrichment process and it will create the upward family linkage which can be optionally brought in, constructed automatically during the account enrichment process, and visualized as a parent/child hierarchy. In our project the specific ask from the client is to not create any parent/child hierarchy because if we create parent child hierarchy then the corresponding parent/child profiles will get created in the tenant which is restricted here but we need to store the hierarchical data in Reltio (without creating profile). So to achieve this requirement we can store this hierarchical information either in Nested attributes or reference Attributes. In a small discussion with Reltio we got the suggestion If we create reference entity it would be easy to master and update in 1 place. Example we get Walmart as global parent for 20 records, storing as reference entity will help us to modify Walmart to Walmart Corp at only 1 place

• Ask 1: Verification of Understanding: Please validate our understanding that the native connectors, such as the Reltio D&B connector (getMatch and getCompanyDetails api), will be able to store data in Reltio MDM Entity as nested attributes.
• Ask 2: Inquiry on Hierarchical Information Storage: We would like to know if there is any Reltio native connector available that stores Hierarchy information as a reference attribute.
• Ask 3: Implementation Guidance: We seek Reltio's additional guidance on how to best implement this solution using a reference attribute to avoid the creation of new profiles. Could you provide us with best practices, steps, or strategies to achieve this?

If I understood your requirement clearly, ask is to store Hierarchy details without creating new profiles. This can be achieved with minimal customization in new D&B datablocks connector https://docs.reltio.com/en/integrate/reltio-data-enrichment-integrations/reltio-enrichment-with-db-data-blocks. 
Regarding reference attribute: As Gaurav mentioned reference attribute are nothing but reference of another records hence you can't have a reference attribute without actually creating the profile. 

Hi Team,

Can you please help us with the resolution of the below usecase.

Use Case : We are loading Organization data in Reltio from multiple sources and we are also enriching that data using Reltio D&B connector. We can create Hierarchies and Relationships during the enrichment process and it will create the upward family linkage which can be optionally brought in, constructed automatically during the account enrichment process, and visualized as a parent/child hierarchy. In our project the specific ask from the client is to not create any parent/child hierarchy because if we create parent child hierarchy then the corresponding parent/child profiles will get created in the tenant which is restricted here but we need to store the hierarchical data in Reltio (without creating profile). So to achieve this requirement we can store this hierarchical information either in Nested attributes or reference Attributes. In a small discussion with Reltio we got the suggestion If we create reference entity it would be easy to master and update in 1 place. Example we get Walmart as global parent for 20 records, storing as reference entity will help us to modify Walmart to Walmart Corp at only 1 place

• Ask 1: Verification of Understanding: Please validate our understanding that the native connectors, such as the Reltio D&B connector (getMatch and getCompanyDetails api), will be able to store data in Reltio MDM Entity as nested attributes.
• Ask 2: Inquiry on Hierarchical Information Storage: We would like to know if there is any Reltio native connector available that stores Hierarchy information as a reference attribute.
• Ask 3: Implementation Guidance: We seek Reltio's additional guidance on how to best implement this solution using a reference attribute to avoid the creation of new profiles. Could you provide us with best practices, steps, or strategies to achieve this?

Hi @Ashish Rawat,

This is to inquire about the integration specifics of our current OOTB D&B datablocks recipe. Specifically, I am interested in understanding whether the mapping of Reltio attributes to D&B attributes is included as part of the standard configuration of this recipe. Or we need to perform JOLT transformation mapping in a similar note of  OOTB Real-time D&B Reltio API.

If I understood your requirement clearly, ask is to store Hierarchy details without creating new profiles. This can be achieved with minimal customization in new D&B datablocks connector https://docs.reltio.com/en/integrate/reltio-data-enrichment-integrations/reltio-enrichment-with-db-data-blocks. 
Regarding reference attribute: As Gaurav mentioned reference attribute are nothing but reference of another records hence you can't have a reference attribute without actually creating the profile. 

Hi Team,

Can you please help us with the resolution of the below usecase.

Use Case : We are loading Organization data in Reltio from multiple sources and we are also enriching that data using Reltio D&B connector. We can create Hierarchies and Relationships during the enrichment process and it will create the upward family linkage which can be optionally brought in, constructed automatically during the account enrichment process, and visualized as a parent/child hierarchy. In our project the specific ask from the client is to not create any parent/child hierarchy because if we create parent child hierarchy then the corresponding parent/child profiles will get created in the tenant which is restricted here but we need to store the hierarchical data in Reltio (without creating profile). So to achieve this requirement we can store this hierarchical information either in Nested attributes or reference Attributes. In a small discussion with Reltio we got the suggestion If we create reference entity it would be easy to master and update in 1 place. Example we get Walmart as global parent for 20 records, storing as reference entity will help us to modify Walmart to Walmart Corp at only 1 place

• Ask 1: Verification of Understanding: Please validate our understanding that the native connectors, such as the Reltio D&B connector (getMatch and getCompanyDetails api), will be able to store data in Reltio MDM Entity as nested attributes.
• Ask 2: Inquiry on Hierarchical Information Storage: We would like to know if there is any Reltio native connector available that stores Hierarchy information as a reference attribute.
• Ask 3: Implementation Guidance: We seek Reltio's additional guidance on how to best implement this solution using a reference attribute to avoid the creation of new profiles. Could you provide us with best practices, steps, or strategies to achieve this?

Hi @Ashish Rawat,

This is to inquire about the integration specifics of our current OOTB D&B datablocks recipe. Specifically, I am interested in understanding whether the mapping of Reltio attributes to D&B attributes is included as part of the standard configuration of this recipe. Or we need to perform JOLT transformation mapping in a similar note of  OOTB Real-time D&B Reltio API.

If I understood your requirement clearly, ask is to store Hierarchy details without creating new profiles. This can be achieved with minimal customization in new D&B datablocks connector https://docs.reltio.com/en/integrate/reltio-data-enrichment-integrations/reltio-enrichment-with-db-data-blocks. 
Regarding reference attribute: As Gaurav mentioned reference attribute are nothing but reference of another records hence you can't have a reference attribute without actually creating the profile. 

Hi Team,

Can you please help us with the resolution of the below usecase.

Use Case : We are loading Organization data in Reltio from multiple sources and we are also enriching that data using Reltio D&B connector. We can create Hierarchies and Relationships during the enrichment process and it will create the upward family linkage which can be optionally brought in, constructed automatically during the account enrichment process, and visualized as a parent/child hierarchy. In our project the specific ask from the client is to not create any parent/child hierarchy because if we create parent child hierarchy then the corresponding parent/child profiles will get created in the tenant which is restricted here but we need to store the hierarchical data in Reltio (without creating profile). So to achieve this requirement we can store this hierarchical information either in Nested attributes or reference Attributes. In a small discussion with Reltio we got the suggestion If we create reference entity it would be easy to master and update in 1 place. Example we get Walmart as global parent for 20 records, storing as reference entity will help us to modify Walmart to Walmart Corp at only 1 place

• Ask 1: Verification of Understanding: Please validate our understanding that the native connectors, such as the Reltio D&B connector (getMatch and getCompanyDetails api), will be able to store data in Reltio MDM Entity as nested attributes.
• Ask 2: Inquiry on Hierarchical Information Storage: We would like to know if there is any Reltio native connector available that stores Hierarchy information as a reference attribute.
• Ask 3: Implementation Guidance: We seek Reltio's additional guidance on how to best implement this solution using a reference attribute to avoid the creation of new profiles. Could you provide us with best practices, steps, or strategies to achieve this?