Reltio enrichment with D&B and addresses
Learn how the D&B connector works with addresses.
The Reltio Enrichment with D&B supports addresses as nested and reference attributes. Default mapping requires that an address must have the AddressType lookup and a primary boolean attribute.
The connector uses the AddressType.lookupCode in all default mappings, and not AddressType.value.
So, how does Reltio Enrichment for D&B choose and work with addresses? Here's the logic:
| Address associated with the account | Address used |
|---|---|
| One address | Used by default |
| One shipping address | Used by default |
| One billing address | Used by default |
| Multiple addresses and one shipping address | Shipping address used by default |
| One shipping address and one billing address | Shipping address used by default |
| Multiple shipping addresses | Address marked as primary |
| Multiple addresses and one billing address | Billing address used by default |
| Multiple billing addresses | Address marked as primary |
Errors, if any, occur in one of these circumstances:
There is no address associated with the account.
There are multiple billing or shipping addresses associated with the account, but none of them is defined as the primary account.
There are multiple addresses associated with the account without the lookup type defined, so the connector isn't able to recognize the type.