Hi Chandra,
Search for reference attributes is exactly the same as searching for any other types of attributes. Basically, the examples provided in our portal is what you would use. Search for reference attributes has no difference from the search for simply invested attributes, and that's the power of reference attributes. And this is oftentimes this is why reference attributes appear in the model. Oftentimes, they hear that a specific reference attribute was present in the data model just to represent the relationship and provide the search capability for it.
Specifically, on the search API, which is across all API, reference attributes is one of the most impactful search terms. You'll have very different latency on your search API, as well as on save API, if compared, if you have an entity with just one reference attribute, compared to the same entity with just 10 reference attributes, it will be several times higher latency on it.
But rather than that, the search of reference attributes is exactly the same. So you just put the attribute name, which is the way you would put the simple attribute name. Search will work exactly the same way, for all the search APIs, across all search APIs.
------------------------------
Dmitry Blinov
Principal Product Manager
Reltio
------------------------------
Original Message:
Sent: 03-21-2023 16:34
From: Chandra Bonthu
Subject: Endpoint URL example for entity search with reference attributes
Can anyone share an endpoint URL example for entity search with reference attributes?
------------------------------
Chandra Bonthu
Associate Director - Master Data Management and Data Quality
Syneos Health
Raleigh-Durham NC
------------------------------