Reltio Connect

Hi there members,

Do we have any option in Reltio to restrict the data that is populated in the drop down when using a reference attribute?

Example: Let's say there is an entity type for Company and another entity type for Technology. If in case, I'm using the Technology entity type as a reference in Company entity type, I want to provide a constraint to my reference, asking it to pull only those profiles of Technology entity type having an attribute called description as Python. 

Because, as we closely scale Reltio in migrating data from RDBMS and Non-RDBMS, it is high time to enable flexibility in L3 to pull the only the desired output when populating attributes.

Hi Nidheesh,

I agree that this would be a great feature.  My suggestion is that you create an Aha! idea and ask others to vote for it via the community.  Doing so will definitely attract the attention of the product team.

If you had a custom UI, you would be able to do this filtering in your presentation layer.  It may be possible to do something like this with a custom facet.  I don't know, I haven't tried.

If you want to restrict yourself to out of the box capabilities, you may be able to put something together using the new conditional attribute functionality and having multiple lookups.  The downside of this approach is the added maintenance and the fact that the lookup is stored across multiple attributes. The fact that Reltio only presents attributes that have values when performing a GET might make it useful in your use case.

If you decide to create the Aha!, I know I'd vote for it!

Thanks for all the suggestions @Gino Fortunato. There are few other questions of mine which didn't get enough attention. Can you please help in checking out those too?

Auto-populating simple attribute from reference attribute | Reltio Connect

Display generator as a text field | Reltio Connect

Reltio icon pack - share request | Reltio Connect

I will create an idea for all those needed upon confirmation from Reltio if any of the feature is yet to be implemented.