Reltio Connect

Hi Team,

We have received a request from the client to create around 150+ attributes in a entity.

Please let us know if anyone has come across to create this number of attributes in an entity.

Let us know any disadvantages that we might have to discuss with client or any pitfalls with such a large no of attributes for an entity.

Thank you.

------------------------------
Sridhar Raju
Manager
PricewaterhouseCoopers
------------------------------

The impacts I'd watch out for are;

1. Payload size exceeded on the event bus.  You  should monitor the size and consider using "snapshot with selected fields"
2. UI usability.  (i.e. Profile layout "crowding", number of search facets,  creating/updating entities, etc.). 
3. Impacts to DG processes (evaluating Potential Matches)
4. Complexity or quantity of required match rules

Number of defined attributes isn't an issue per se, you need to determine % of populated attributes.  If the entities are sparsely populated Reltio does a good job of mitigating the impacts.  Also the type of attributes makes a difference (Simple, nested, reference).  You should review Configuration Best Practices  at a minimum you'll know what will be flagged during an engineering review.

------------------------------
Robert Quinn
Data Management Practice Lead
imidia LLC
Basking Ridge NJ
------------------------------