Is it possible to add such conditional logic within the D&B Datablocks RIH recipes?

Question:

1. Is it possible to add such conditional logic within the D&B Datablocks RIH recipes?
2. Can you provide documentation or examples for implementing this logic?

Answer: 

Yes, it is possible to incorporate conditional logic within the D&B Datablocks batch enrichment recipes in Reltio Integration Hub (RIH) to restrict the invocation of the "get match" API only to profiles that have already been enriched.
 
The Reltio D&B enrichment process utilizes RIH recipes, which can be customized to include specific conditions. To achieve your requirement, you can modify the batch enrichment recipe to include a filter that selects only those profiles that have been previously enriched. This can be done by leveraging Reltio attributes or audit logs that indicate prior enrichment.
 
For instance, you can adjust the "filter" parameter in the batch enrichment API call to target only entities with a specific attribute or flag set during previous enrichment processes. This ensures that the "get match" API is invoked only for those profiles.
 
Here's how you can modify the batch enrichment API call:

POST https://apim.workato.com/XXXXXXXXXX/trigger-recipes/batchEnrichment?filter={{filter}}&doNotMerge={{flag}}
Headers:
  api-token: <Your Auth Token>
  Content-Type: application/json

In this call, replace {{filter}} with a condition that selects only previously enriched profiles, such as those with a specific attribute value.
 
For detailed guidance on configuring batch enrichment and applying filters, refer to the official Reltio documentation:

• Configure batch mode

This documentation provides insights into setting up batch processes and applying filters to target specific entities.
 
Additionally, the community discussion on Batch Enrichment via D&B datablock may offer practical examples and shared experiences from other users who have implemented similar conditional logic. community.reltio.com
By customizing the batch enrichment recipe with appropriate filters, you can effectively control the invocation of the "get match" API, ensuring it is called only for profiles that meet your specified criteria.

When initiating a batch enrichment process using the D&B connector in Reltio, the system performs both matching and enrichment operations on the selected records. This means that even if a record has already been enriched and possesses a DUNS number, the process may still invoke the "get match" API to confirm or update the match information. This behavior is inherent to the batch enrichment process and is designed to ensure that the most accurate and up-to-date information is associated with each record. https://docs.reltio.com/en/developer-resources/data-integration-apis/data-integration-apis-at-a-glance/db-connector-apis/batch-apis
 
To control which records undergo the enrichment process, you can apply filters based on specific attributes. For instance, if you want to enrich only those records that have not been previously enriched, you can use the Data Provider Verification Status attribute as a filter criterion. By setting the filter to select records where this attribute does not equal "Enriched by Dun & Bradstreet," you can effectively target only new or updated records for enrichment.
Here's how you might structure the API call with such a filter:

POST https://apim.workato.com/XXXXXXXXXX/trigger-recipes/batchEnrichment?filter=not(equals(attributes.DataProviderVerificationStatus, 'Enriched by Dun & Bradstreet'))&doNotMerge=true
Headers:
  api-token: <Your Auth Token>
  Content-Type: application/json

 
This approach ensures that only records not previously enriched are processed, thereby avoiding unnecessary matching operations on already enriched records.
 

• Re-enrichment of Specific Records: If you need to re-enrich specific records (e.g., due to changes in enrichment logic or data corrections), you should first remove or clear the Data Provider Verification Status attribute for those records. This action signals the system that these records require re-enrichment. docs.reltio.com
• Inherent Matching Behavior: Even with filters applied, the batch enrichment process may still perform matching operations on the selected records. This is because the process is designed to validate and update match information to maintain data accuracy.

• Applying filters based on attributes like Data Provider Verification Status allows you to control which records are selected for enrichment.
• To re-enrich specific records, clear the relevant status attributes to include them in the enrichment process.
• Be aware that the batch enrichment process inherently includes matching operations to ensure data accuracy, even for records that have been previously enriched.

References:

https://docs.reltio.com/en/applications/data-integrations/data-enrichment-integrations-at-a-glance/reltio-enrichment-with-db-data-blocks-at-a-glance/reltio-enrichment-with-db-data-blocks-set-up/faq-for-reltio-enrichment-with-db-data-blocks

https://docs.reltio.com/en/developer-resources/data-integration-apis/data-integration-apis-at-a-glance/db-connector-apis/batch-apis

https://community.reltio.com/discussion/batch-enrichment-via-db-datablock

https://community.reltio.com/discussion/batch-enrichment-via-db-datablock