Dun & Bradstreet (D&B) data should be treated as enrichment data of existing customers and should not be modeled as a source system. This is due to certain system constraints, such as enforcing a unique source system and source record ID combination, which will likely not be the case when maintaining D&B data. It is unlikely that multiple customers will not have a shared D-U-N-S Number, which breaks the uniqueness constraint within the match and merge model.
By default, D&B data is stored and maintained on a separate object, rather than on the actual customer record. A reference then connects the two objects for association between customer data and D&B data. It is often desirable to view specific D&B data directly on a customer record. To achieve this, it is recommended to use a business rule after the enrichment request has been executed. This business rule can then copy selected D&B data back to the customer record for easier viewing. For a comprehensive review of all D&B enrichment data, navigate to the D&B record itself.
D&B matching can also be included as part of the inbound Match and Merge Importer. For this use case, the asynchronous process should be used. This will allow for new incoming customers to be matched by D&B and assigned a D-U-N-S Number. Customers that require a candidate to be selected will be placed into the select candidate state of the D&B match workflow and await user review.