Reltio Connect

Hi everyone,

I am working on loading Customer to Customer (C2C) relationships into Reltio and I could use some guidance from people who have handled similar scenarios.

Here is the context.
In our source system, we have several relationship combinations across Person to Person, Business to Business, and Business to Person. When we profiled the data, we found around twenty-five distinct relationship types across these combinations. For example, relationships like husband and wife, parent and child, business affiliate, and so on.

The challenge I am running into is with the data load design. In Reltio, each relationship type typically becomes its own relationship entity. Which means if I have 25 relationship types, I will end up creating 25 separate relationship objects and in turn generating 25 separate extract files for loading. This becomes hard to maintain over time and seems inefficient, especially when most of the attributes and structure are identical across these relationship types.

My question is simple. What is the recommended approach for handling this kind of scenario. Do most teams create separate relationship objects for each relationship type and maintain separate files for every load? Or is there a cleaner pattern that allows us to load multiple relationship types through a single template while still keeping the configuration manageable on the Reltio side?

Any guidance or examples from your implementations would be really helpful.

Thank you in advance.

Hi Rushyendar,

Great question!  In my opinion, the problem boils down to the need for this level of detail.  It was designed into your source, so it seems like it is required there.  But is it needed for your business use cases that the organization is trying to solve with MDM?  If not, you may be able to consolidate some of them into more generic 'spouse', 'sibling', 'organization affiliate'.  But if you do this consolidation, you are going to have to figure out how to push them back to the source in a way the source will understand (assuming two way integrations)