Unify and manage your data

Prerequisites for Reltio Enrichment with D&B Data Blocks

Review the product entitlements, licensing, and platform prerequisites before you configure Reltio Enrichment with D&B Data Blocks.

Product requirements

Your tenant must be provisioned with the B2B or Financial Services velocity pack, or equivalent attribution configured to support D&B Data Blocks mappings.

Licensing

  • Reltio licensing — You need entitlements for Reltio Enrichment with D&B and Reltio Integration Hub. Contact your Reltio representative for licensing details.
  • D&B licensing — To access D&B Data Blocks data, you need a valid D&B license and API credentials (API key, username, password). This prebuilt integration supports the following:
    • Company Information Level 3 V1: Company Information like communication details, key financial figures, industry codes, etc.

    • Hierarchies & Connections Level 1 V1: Contains corporate hierarchy details.

    • Diversity Insights Level 1 V1: Contains SocioEconomic Information.

    • Principals & Contacts Level 1 V2: Contains details of principal contact of the organization.

Roles and permissions

  • At least one administrator must be assigned the ROLE_INTEGRATION_CUSTOMER_ADMIN role to manage integrations in Reltio Integration Hub.
  • Assign the ROLE_DNB_CONNECTOR role to users who need to run on-demand enrichment through UI buttons.

For more information on roles and access, see topic Integration Hub set up.

Tenant prerequisites

  • For real-time enrichment, configure a dedicated SQS queue separate from your tenant’s standard queue.
  • Apply recommended event filters:
    • Type filter: ENTITY_CHANGED, ENTITY_CREATED
    • Object filter: (equals(type,'configuration/entityTypes/Organization') and (not equals(sourceSystems,'DnB')))
  • Enable Search by OV in the tenant configuration.
  • Configure the Monitoring Registration Reference ID property.
  • Set up and configure an AWS S3 bucket for the D&B Monitoring process.

Client credential prerequisites

You must create a dedicated client credential to act as a service account. This account is used by recipes to extract and write D&B data.
  • Minimum scope: ROLE_API
  • If metadata security is enabled, grant additional permissions to CREATE, READ, UPDATE, DELETE, MERGE, UNMERGE the following:
    • Entities: Organization, Individual, Location
    • Relationships: DnBHierarchy, OrganizationHasAddress, IndividualEmployer

Example client credential configuration:

{
   "clientId": "DNB_DataBlocks_Enrichment_Process",
   "scope": [
      "ROLE_API",
      "CUSTOM_ROLE_WITH_METADATA_PERMISSIONS"
   ],
   "authorities": [],
   "resourceIds": [],
   "authorizedGrantTypes": [
      "client_credentials"
   ],
   "clientDescription": "Used in tenant for D&B Data Blocks Enrichment",
   "clientName": "Client",
   "clientEmail": "email@email.com",
   "redirectUri": [],
   "accessTokenValidity": 3600,
   "refreshTokenValidity": null,
   "clientAuthenticationMethods": [
      "client_secret_post",
      "client_secret_basic"
   ],
   "enabled": true
}