D&B Data Storage

The Dun & Bradstreet (D&B) integration automatic mapping from the D&B data received and the STEP D&B Organization is performed by the 'executeBusinessActionWithDnbIntegrationContext()' method in the business actions. The Easy Setup uses this method by default.

  • Details about the default data stored and the mapping between the D&B model and the STEP model can be found in the D&B Attributes and Data Containers section here.

  • To store additional data, business actions can be extended using JavaScript. Refer to the Scripting API documentation, which is accessible via the Technical Documentation at [system]/sdk or from the system Start Page.

As shown in the numbered list below, D&B data is stored when matching (1) and enriching (2). Data can also be stored during re-matching (3), for example, when a second customer organization matches on one or more of the same D&B Organization entities that already exist in STEP.

  1. Matching: The data returned from D&B is limited but enough to identify the organization. The data is stored on newly created D&B Organization entities.

  2. Enriching: Detailed data is fetched and stored on the D&B Organization entity. All existing data from the matching request is overwritten, including all instances of multivalued data containers to ensure all data is relevant and up to date.

  3. Re-Matching: When storing the limited set of matching data on existing, already enriched, D&B Organization entities, the following rules apply:

  • For attributes and single valued data containers, the data is stored one-to-one, overwriting any existing data.

  • For multivalued data containers, an algorithm ensures existing (enrichment) data is not overwritten by comparing the new data with existing data on the data container. If there is a full match (the received subset of data is the same as the existing), nothing is updated. If there is not a full match, a new data container instance is created. No existing data container instances are ever deleted.

Note: If using more than one D&B enrichment product, the default enrichment mapping from the D&B data model to STEP is only used for the first enrichment. Any subsequent use can overwrite the previous enrichment data.

For information about migrating from D&B V2 to Direct+, refer to the Dun & Bradstreet Migration: Direct 2.0 to Direct+ topic in the System Administration documentation here.