FAQ for Reltio Enrichment with D&B (Data Blocks)
Frequently Asked Questions about RIH: DnB Data Blocks integration.
1. Does this product require licensing?
Yes, this product requires licensing. For more information, see topic Licensing.
2. What modes of enrichment should I use?
It is recommended to use Batch Mode at least one time during your Reltio implementation lifecycle. Typically this occurs after the initial data load and consolidation/mastering. The batch mode supports enrichment of profiles in bulk and has a configurable filter condition which allows you to enrich the superset or some subset of data.
After the initial Batch enrichment is complete, you may choose to adopt Monitoring and monitor the superset or subset of data. You’ll receive these ‘push’ updates from D&B with no further action required on your end.
Alternatively, you may choose to adopt Real-Time (continuous) enrichment instead. It is recommended to use a dedicated SQS streaming destination for this purpose. It is recommended to set Type filter and Object filter for these events to suit your business requirements and reduce the amount of processing and RIH tasks invoked.
For example, set Type filter to ENTITY_CREATED, ENTITY_CHANGED
and Object filter to (equals(type,'configuration/entityTypes/Organization') and (not equals(sourceSystems,'DnB')))
.
3. What modes of enrichment support re-enrichment of records?
Re-enrichment will work only for On-Demand Enrichment via Rest API and Monitoring (For Monitoring, doNotMerge
flag won’t be considered).
For records already containing enrichment D&B crosswalks like URI:DUNS that need to be enriched, if the job ran with doNotMerge
flag as true
, the recipe will not process this record and an error message is thrown in the D&B Logs table. If the job ran with doNotMerge
flag as false
with the Confidence Code less than Auto Merge – Confidence Code, the recipe will not process this record and an error message is thrown in the D&B Logs table.
In this case, if we must force re-enrichment of records, then the Data Provider Verification Status value attribute should be deleted/removed for specific enriched records from Reltio. Then, if a Batch job is run and part of the filter criteria, it will re-enrich those records.
4. Why can’t I see the On-Demand buttons?
Ensure you have ROLE_DNB_CONNECTOR
assigned to you and the On-Demand configuration was performed.
You’ll need a Reltio support ticket to create the RIH profile that is used by the UI configuration.
5. Where can I see D&B Integration recipe task counts?
You can view the recipes task count in the Dashboard menu in RIH. Specify filters to view relevant details, as shown in the screenshot below:
6. Where can I find job status and logs?
7. How do I activate a particular mode of enrichment?
See topic Configure Reltio Enrichment with D&B (Data Blocks)
8. Can I use an external application to trigger or schedule batch and/or on-demand enrichment for data in my Reltio tenant?
Yes. Enable Batch or Real-Time APIs and their corresponding triggers. Create an authorization token for these APIs and begin making requests to these endpoints.
For more details, see topic Configure Reltio Enrichment with D&B (Data Blocks)
9. Can I modify recipes?
Yes. If you are adding new Data Blocks, see topic Customize or Add New Data Blocks.
Reltio cannot provide support for customizations.
10. Where are the rest of my logs?
RIH has limitations of 10,000 entries per Lookup table. If the D&B Job Execution Statistics
or D&B Logs
lookup table reaches 9,900 entries, the last 1,000 old entries will be deleted from these lookup tables (Step 19, Step 23). Other Lookup tables will be truncated while starting any new job. For more details, see topic Operate Reltio Enrichment with D&B (Data Blocks)
11. What do the On-Demand (UI buttons) do?
12. What happens to logs for Jobs that are terminated or stopped abruptly?
You cannot view logs and stats for a job that is either terminated or stopped abruptly.
13. Why aren't principal contacts being added?
To enrich a record with the Principal Contacts datablock, ensure one of the 3 datablocks, i.e. Company Info, Hierarchy connections, or Diversity Insights, is mandatory.
If the Principal contact and Hierarchy datablocks are available, and hierarchy is not available for the record from D&B, then the Hierarchy is unavailable for these records hence Principal contacts won't be created error message is logged. If all datablocks are present and the hierarchy is not available for the record, the principal contacts are populated for the record along with the company details.
14. Can I match multiple profiles to the same Organization (DUNS Number)?
Yes, you can but with some limitations on hierarchy and contacts.
Let us assume there are 2 duplicate records in Reltio. The first one is already enriched and contains crosswalks such as URI:DUNS, Standalone DUNS. The other record that must be enriched will also get same DUNS Number. To avoid merging 2 duplicate records based on Standalone DUNS crosswalks, only URI:DUNS crosswalk will be created for the duplicate record.
If Hierarchy and Principal Contacts is available, it will be skipped for the duplicate record. In other words, only the first enriched record will contain these details.
15. How can I enrich Shell Records (created for Hierarchy)?
The recipes won’t allow the enrichment of Parent records via Real-Time and Batch. These records will be ignored and captured under logs for Batch Process.
Shell Records can be enriched using On-Demand or when subscribed to Monitoring. Contact your D&B Representative for more information regarding monitoring.
16. How does Monitoring work?
The Monitoring feature provides the ability to receive the updates/changes that occurred to the specific registered DUNS Numbers. To create a Monitoring registration - Link, customers should work with their Dun & Bradstreet Representative to have registrations created or raise support ticket with https://support.dnb.com:
-
DUNS Status type - The Status types - SEED, TRANSFER, UNDELETE, DELETE are processed from Monitoring recipes. The other types are ignored and captured under Failed records.
-
Based on DUNS Number Attribute and Crosswalks – URI:DUNS, DUNS in Reltio, the records will be processed from Monitoring files. If that attribute and crosswalks are missing in Reltio for the records, then those records will be captured under Failed records. SEED, TRANSFER, DELETE – the records will be processed only if that DUNS attribute and crosswalks values is ov: “true” in Reltio.
-
SEED - Company Info and Diversity Insight details will be updated for the records having URI:DUNS as a crosswalk. Hierarchy and Principal Contacts will be updated only for the records having DUNS as a crosswalk.
-
TRANSFER – Will Soft delete the old D&B crosswalks by adding deleteDate and will create new D&B crosswalks from the retainedDUNS value. The Transferred DUNS details will be captured in D&B Logs table. User have to register the retainedDUNS for getting the updates from D&B Monitoring.
-
DELETE – Will Soft delete all the D&B crosswalks by adding deleteDate.
-
UNDELETE – Will remove the deleteDate from all D&B crosswalks which got already soft deleted.
-
EXCEPTION File – The DUNS number captured in EXCEPTION files will be written to “D&B Logs” Lookup Table.
17. How can I deploy the D&B Data Blocks integration into my tenant?
After obtaining the necessary entitlements, contact Reltio Support to have the deployment done for a given tenant.
After the deployment is complete, you may proceed with the configuration. For more details, see topic Configure Reltio Enrichment with D&B (Data Blocks).
18. Why do we have different crosswalk formats?
Crosswalk Sources | Crosswalk Values | Record Type | Description | Verification Status/Details | |
---|---|---|---|---|---|
Entity | Dun & Bradstreet | URI:DUNS | Auto Merged Record | URI:DUNS - is used for populating Company info details. URI in the crosswalk ensures all records can be enriched to avoid unique DUNS dependency. Also solves the infamous/painful "URI miss match" issue of past connector. Standalone DUNS crosswalk- is used for creating Hierarchy and Contacts relationships. Standalone DUNS crosswalk will be populated only for one Auto merge record. | Enriched |
Dun & Bradstreet | DnB/URI | Source Record | In case of No Match Found, Potential Match and any error from D&B, we will create this crosswalk in original record. Later, if the record is enriched successfully then this crosswalk will be soft deleted. | No Match Found, Potential Match Found, Error occurred in D&B job | |
Dun & Bradstreet | URI:DUNS | Potential Match Record | For Source records, this record will be created as a Potential Match record, if confidence code is between Auto Merge – Confidence Code and Potential Match – Confidence Code. | Enriched | |
Dun & Bradstreet | URI:DUNS | Duplicate Record | For duplicate records when we try to enrich, only Company info details will be populated from this crosswalk. Standalone DUNS crosswalks will not be created, and we will get the Verification Details message. | Data Provider Verification Details - Hierarchy and Principal Contact is unavailable for this duplicate entity. Resolve merge with Entity ID | |
Dun & Bradstreet | DUNS+MSP+GIVEN NAME | Principal Contacts | If a contact is created while enrichment, then we’ll create crosswalk in this pattern for that contact record. DUNS - Associated to Organization, MSP – Most Senior Principals abbreviation is used in crosswalk. GIVEN NAME – Associated to Principal Contacts. | NA | |
Dun & Bradstreet | DUNS | Parent | In case of Hierarchy enrichment, if the Parent DUNS is not already present in Reltio, then we will create shell records with that Parent DUNS as a crosswalk. This shell record contains Name, Address, DUNS Number in attribute level. | NA | |
Relation | Dun & Bradstreet | DUNS:DUNS | Organization – Organization | Parent DUNS:Child DUNS | NA |
Dun & Bradstreet | DUNS:DUNS+MSP+GIVEN NAME | Organization – Individual | DUNS:Contact Crosswalk | NA | |
Dun & Bradstreet | AddressType:URI|DUNS | Organization – Location | Example - Shipping:URI|DUNS | NA |
19. Do you have any Performance Benchmarks?
Enrichment Mode | Record Count | Duration |
---|---|---|
On-Demand: Get Match | 1 | 7 sec |
On-Demand: Get Company Details | 1 | 5 sec |
On-Demand: Get Company Hierarchy and Contacts | 1 | 5 sec |
Real Time | 1 | 5 sec |
Batch | 100K | 1 hr 10 mins |
Batch | 50K | 35 mins |
Batch | 10K | 10 mins |
The above stats are the results of performance testing. The duration of job depends on Reltio tenant performance and D&B response. Hence the stats may differ from customer to customer.
20. How can I deploy the D&B Data Blocks integration into my tenant?
After obtaining the necessary entitlements, contact Reltio Support to have the deployment done for a given tenant.
After the deployment is complete, proceed with to Configure Reltio Enrichment with D&B (Data Blocks).
21. Why do we have different crosswalk formats?
Different crosswalk formats are used to address various data integration scenarios. The following table describes the crosswalk sources, values, and verification details:
Crosswalk Sources | Crosswalk Values | Record Type | Description | Verification Status/Details |
---|---|---|---|---|
Dun & Bradstreet | URI:DUNS | Auto Merged Record | URI:DUNS is used for populating company info details. | Enriched |
Dun & Bradstreet | DnB/URI | Source Record | No Match Found, Potential Match Found, Error occurred in D&B job. | No Match Found, Potential Match Found, Error occurred in D&B job |
Dun & Bradstreet | URI:DUNS | Potential Match Record | For Source records, this record will be created as a Potential Match record. | Enriched |
Dun & Bradstreet | URI:DUNS | Duplicate Record | Only Company info details will be populated from this crosswalk. | Data Provider Verification Details |
Dun & Bradstreet | DUNS+MSP+GIVEN NAME | Principal Contacts | Associated to Organization, MSP, and Principal Contacts. | NA |
Dun & Bradstreet | DUNS | Parent | Shell records created with Parent DUNS as a crosswalk. | NA |
Dun & Bradstreet | DUNS:DUNS | Organization – Organization | Parent DUNS:Child DUNS | NA |
Dun & Bradstreet | DUNS:DUNS+MSP+GIVEN NAME | Organization – Individual | DUNS:Contact Crosswalk | NA |
Dun & Bradstreet | AddressType:URI|DUNS | Organization – Location | Example - Shipping:URI|DUNS | NA |
22. Do you have any Performance Benchmarks?
The following table provides performance benchmarks for different enrichment modes:
Enrichment Mode | Record Count | Duration |
---|---|---|
On-Demand: Get Match | 1 | 7 sec |
On-Demand: Get Latest Company Details | 1 | 5 sec |
On-Demand: Get Company Hierarchy and Contacts | 1 | 5 sec |
Real Time | 1 | 5 sec |
Batch | 10K | 10 mins |
Batch | 50K | 35 mins |
Batch | 100K | 1 hr 10 mins |
23. Can I use Hierarchy & Connections Data Block without creating the organization profiles and relationships in Reltio?
This is not a supported use-case out-of-the-box, although recipes can be customized to modify the functionality.
24. Using Monitoring, what happens to the data in Reltio when an organization's DUNS number changes?
For monitoring, D&B sends a Transfer status instead of Seed. Based on the status, the integration will soft delete the old DUNS and append new DUNS crosswalks to the same profile.
To receive further updates, the new DUNS number will need to be added to the monitoring registration.