Reltio Connect

Hi Team,

Just brainstorming on a requirement, I am planning to use Reltio search filter as an input for my Recipe where my trigger is On-Demand basis.
It is working fine for small numbers, but i am not in a condition to run huge numbers in Dev.
But in Production, we are planning to refresh around 100k records. 

Any suggestions, if i need to consider while testing regarding Pagenation / Looping.

Thanks & Regards

Hi Chetan,

Search API is helpful if the dataset you are working on/retrieving is less than 10K. As the Search API cannot retrieve data if the count exceeds 10K.

Entity Search | Reltio

Instead you can use Entities Scan API and set this up using Custom Action of Reltio Connector. Using cursor you can easily get n number of records based on the search filter applied.

Check the documentation: Search Entity with Cursor | Reltio

Hi Team,

Just brainstorming on a requirement, I am planning to use Reltio search filter as an input for my Recipe where my trigger is On-Demand basis.
It is working fine for small numbers, but i am not in a condition to run huge numbers in Dev.
But in Production, we are planning to refresh around 100k records. 

Any suggestions, if i need to consider while testing regarding Pagenation / Looping.

Thanks & Regards

Thanks for the response @Sheshadri V.
I had a look at the documentation and i have few more questions.

1. Does it work even if we are targeting to consider > 500k profiles
   Example - We are trying to enrich based on few conditions where dataset we plan to consider comes >500k
2. Currently i see below actions in RIH (Reltio Connection)
   1. Add Record to Entity
   2. Apply data changes request
   3. Create record
   4. Create record in bulk
   5. Decrypt Export URL
   6. Delete Entities as Not a Match
   7. Delete Potential Match
   8. Delete Record
   9. Delete Record in Bulk
   10. Export Records
   11. Get Internal task Status by ID
   12. Get Entities as not a Match
   13. Get Entities by crosswalk
   14. Get Entity by crosswalk
   15. Get potential match for entity
   16. Get records by ID
   17. Get task status by ID
   18. Mark entities as Not a match
   19. Match entities
   20. Merge entities
   21. Reject data change request
   22. search data change request
   23. search records 
   24. set entity are potential match
   25. Unmerge entities
   26. Unmerge entities tree
   27. Update record
   28. Custom action
       
       Could you please suggest a way we find an action to perform based on Scan approach as per our discussion

Thanks & Regards,

Hi Chetan,

Search API is helpful if the dataset you are working on/retrieving is less than 10K. As the Search API cannot retrieve data if the count exceeds 10K.

Entity Search | Reltio

Instead you can use Entities Scan API and set this up using Custom Action of Reltio Connector. Using cursor you can easily get n number of records based on the search filter applied.

Check the documentation: Search Entity with Cursor | Reltio

Hi Team,

Just brainstorming on a requirement, I am planning to use Reltio search filter as an input for my Recipe where my trigger is On-Demand basis.
It is working fine for small numbers, but i am not in a condition to run huge numbers in Dev.
But in Production, we are planning to refresh around 100k records. 

Any suggestions, if i need to consider while testing regarding Pagenation / Looping.

Thanks & Regards

Hi Chetan,

Use can go with 28. Custom action.

Also, if you are planning for very high volumes, make sure to consider the following Limits and Quotas for RIH in Design and implementations:

https://docs.reltio.com/en/explore/get-your-bearings-in-reltio/console/configuration-applications/integration-hub/limits-and-timeouts

Thanks for the response @Sheshadri V.
I had a look at the documentation and i have few more questions.

1. Does it work even if we are targeting to consider > 500k profiles
   Example - We are trying to enrich based on few conditions where dataset we plan to consider comes >500k
2. Currently i see below actions in RIH (Reltio Connection)
   1. Add Record to Entity
   2. Apply data changes request
   3. Create record
   4. Create record in bulk
   5. Decrypt Export URL
   6. Delete Entities as Not a Match
   7. Delete Potential Match
   8. Delete Record
   9. Delete Record in Bulk
   10. Export Records
   11. Get Internal task Status by ID
   12. Get Entities as not a Match
   13. Get Entities by crosswalk
   14. Get Entity by crosswalk
   15. Get potential match for entity
   16. Get records by ID
   17. Get task status by ID
   18. Mark entities as Not a match
   19. Match entities
   20. Merge entities
   21. Reject data change request
   22. search data change request
   23. search records 
   24. set entity are potential match
   25. Unmerge entities
   26. Unmerge entities tree
   27. Update record
   28. Custom action
       
       Could you please suggest a way we find an action to perform based on Scan approach as per our discussion

Thanks & Regards,

Hi Chetan,

Search API is helpful if the dataset you are working on/retrieving is less than 10K. As the Search API cannot retrieve data if the count exceeds 10K.

Entity Search | Reltio

Instead you can use Entities Scan API and set this up using Custom Action of Reltio Connector. Using cursor you can easily get n number of records based on the search filter applied.

Check the documentation: Search Entity with Cursor | Reltio

Hi Team,

Just brainstorming on a requirement, I am planning to use Reltio search filter as an input for my Recipe where my trigger is On-Demand basis.
It is working fine for small numbers, but i am not in a condition to run huge numbers in Dev.
But in Production, we are planning to refresh around 100k records. 

Any suggestions, if i need to consider while testing regarding Pagenation / Looping.

Thanks & Regards

Thanks for the Update, will look on the Best practises and optimise design.
Do you have any use cases where Enrichment was made through RIH .?

Regards,

Hi Chetan,

Use can go with 28. Custom action.

Also, if you are planning for very high volumes, make sure to consider the following Limits and Quotas for RIH in Design and implementations:

https://docs.reltio.com/en/explore/get-your-bearings-in-reltio/console/configuration-applications/integration-hub/limits-and-timeouts

Thanks for the response @Sheshadri V.
I had a look at the documentation and i have few more questions.

1. Does it work even if we are targeting to consider > 500k profiles
   Example - We are trying to enrich based on few conditions where dataset we plan to consider comes >500k
2. Currently i see below actions in RIH (Reltio Connection)
   1. Add Record to Entity
   2. Apply data changes request
   3. Create record
   4. Create record in bulk
   5. Decrypt Export URL
   6. Delete Entities as Not a Match
   7. Delete Potential Match
   8. Delete Record
   9. Delete Record in Bulk
   10. Export Records
   11. Get Internal task Status by ID
   12. Get Entities as not a Match
   13. Get Entities by crosswalk
   14. Get Entity by crosswalk
   15. Get potential match for entity
   16. Get records by ID
   17. Get task status by ID
   18. Mark entities as Not a match
   19. Match entities
   20. Merge entities
   21. Reject data change request
   22. search data change request
   23. search records 
   24. set entity are potential match
   25. Unmerge entities
   26. Unmerge entities tree
   27. Update record
   28. Custom action
       
       Could you please suggest a way we find an action to perform based on Scan approach as per our discussion

Thanks & Regards,

Hi Chetan,

Search API is helpful if the dataset you are working on/retrieving is less than 10K. As the Search API cannot retrieve data if the count exceeds 10K.

Entity Search | Reltio

Instead you can use Entities Scan API and set this up using Custom Action of Reltio Connector. Using cursor you can easily get n number of records based on the search filter applied.

Check the documentation: Search Entity with Cursor | Reltio

Hi Team,

Just brainstorming on a requirement, I am planning to use Reltio search filter as an input for my Recipe where my trigger is On-Demand basis.
It is working fine for small numbers, but i am not in a condition to run huge numbers in Dev.
But in Production, we are planning to refresh around 100k records. 

Any suggestions, if i need to consider while testing regarding Pagenation / Looping.

Thanks & Regards