Reference address

As per the Reltio Velocity Pack, the Address attribute is configured as a reference attribute. Ensure that surrogate key configuration is correctly implemented for all enrichment sources. This ensures stable identity resolution and profile linking.

Disable SQS before bulk loads

Before performing any bulk data loads or updates in Reltio tenants, disable the AWS SQS queue to avoid triggering real-time enrichment recipes. This prevents unintended profile enrichment events and ensures recipe stability during high-volume updates.

API platform subscription

To use the REST API enrichment recipes, customers must subscribe to the API platform in Reltio Integration Hub. This is required for enabling the D&B REST API Collections and making external API calls.

Job termination behavior

If a job is terminated or stopped abruptly, logs and job statistics may be incomplete. Ensure that recipes are stopped using the correct controls to retain full logging details in lookup tables and FileStorage.

Handling unauthorized Data Blocks

If your license does not cover certain Data Blocks, enrichment attempts using those blocks will result in an error. To avoid this:

• Remove unauthorized Data Blocks from the Properties Lookup Table by setting their value to No.
• Remove the Data Blocks from any UI Button configurations in the Organization plugin JSON.

Importing and deploying recipes

After the D&B package is delivered, the Reltio team should import the recipes into a staging tenant. From there, the package should be exported and deployed to customer tenants. This ensures consistency across environments and simplifies governance.

Disabling monitoring recipes

If your subscription does not include monitoring, disable all monitoring-related recipes listed in D&B package artifacts for Reltio Enrichment

Also, set the Automate Monitoring Registration property to No in the Properties Lookup Table to avoid triggering registration flows.

Avoid re-enriching monitoring profiles

After a DUNS is registered for monitoring, avoid triggering re-enrichment on that profile. Reprocessing these records manually or through batch jobs may interfere with D&B-managed workflows and lead to unexpected registration status changes.