Handling of Addresses

Handling of Addresses Between Reltio, D&B and SFDC

There is a fundamental difference in the way that Reltio, Salesforce and D&B handle addresses.

Salesforce address attributes are stored as simple attributes on the Account and Contact objects, and the addresses have a simple 1:1 relationship with the Account and Contact objects.

D&B provides "Primary" and "Mailing" Addresses with a simple 1:1 relationship with the Organization entity.

Reltio Addresses are stored in separate entities that can be linked to the “Organization” and “Contact” entities using a reference attribute that can have a m:m relationship.

Reltio uses the “Address Type” attribute on the HasAddress relationship to manage the mapping of addresses between the three systems as follows:

  • Reltio Organization Address Type:
    • Shipping Address: This is mapped to the D&B “Primary” Address and the SFDC “Shipping” address

    • Billing Address: This is mapped to the SFDC “Billing” address only

    • Mailing Address: This is mapped to the D&B “Mailing” Address only

  • Reltio Contact Address Type:
    • Mailing Address: This is mapped to the SFDC “Mailing” address only.

    • Other Address: This is mapped to the SFDC “Other” address only.

    Note: The D&B Contact (CEO) is not mapped.

Address Attributes Mapping Between the Three Systems

When an address is received from D&B, the PrimaryAddressFlag is set by default for that Address.

Individual address attributes in the three systems are mapped as follows:

D&B Attribute Reltio Attribute SFDC Attribute
AddressType=Shipping
Street Address AddressLine1 Shipping Street
Street Address 2 AddressLine2  
City Name City Shipping City
State/Province Name State Shipping State/Province
Postal Code Postal Code Shipping Zip/Postal Code
Country Name ISO3166-2 Shipping Country
AddressType=Billing
  AddressLine1 Billing Street
  PO Box N/A
  City Billing City
  State Billing State/Province
  Postal Code Billing Zip/Postal Code
  ISO3166-2 Biling Country
AddressType=Mailing
Mailing Street Address AddressLine1  
Mailing Street Address 2 PO Box  
Mailing City Name City  
Mailing State/Province Name State  
Mailing Postal Code Postal Code  
Mailing Country Name ISO3166-2  

Contact Address (From Any Source)

DnB currently does not provide a unique identifier for a contact (e.g. Company CEO), so this attribute is not mapped for D&B. The following approach is used for SFDC:
  • If the Reltio Contact address type = "Mailing", map it to the SFDC Contact "Mailing" address.

  • If the Reltio Contact address type = "Other", map it to the SFDC Contact "Other" address.

  • If the Reltio Contact address type is blank, no action.

Primary Address Flag

Determining the Primary Address for an address type of an organization.

The Primary flag attribute on the HasAddress relationship type determines which address is the primary address.

By default, for an organization record, both Address Type and the Primary flag must be set. If these attributes are not set, then while adding multiple addresses to an organization, you must set this flag to true for one of the addresses for a given address type "Shipping" or "Billing" to determine which address is the primary address. The address with the flag set to true gets synched to SFDC and is used when a match request is sent to D&B.

The following list explains how a Primary Address is determined for an address type in various scenarios:
  • In batch update, if there are multiple addresses and neither the Address Type nor the Primary flag are set, then none of the addresses are treated as a primary address. These addresses are not even sent to D&B for enrichment or synched to SFDC. However, in real time, clicking the Get Match button displays an error message Address not found or Address is incomplete. Please check that Address Type and Primary flag are set.

  • If an organization has only one address and neither its Address Type nor the Primary flag is set, then by default this single address is treated as the primary shipping address for the entity.

  • If an organization has one address with address type of "Shipping" and one address with address type of "Billing", then setting up the Primary flag is not mandatory. By default, these addresses are treated as primary shipping address and primary billing address.

  • If an organization has more than one address of address types "Shipping" and "Billing", but the Primary flag is set to true for only one address, then that one address is treated as the primary address of an address type for the entity.

  • If an organization has multiple addresses and Address Type is specified only for a single address, but the Primary flag is not set to true, then by default this single address is treated as the primary address. The specified address type can be either "Shipping" or "Billing".

  • If an organization has multiple addresses of an address type but the Primary flag is not set to true, then none of the addresses are treated as a primary address.

  • If an organization has multiple addresses of an address type and the Primary flag is set to true for all or more than two addresses, then all such addresses are treated as primary addresses. In such a case, any random address gets synched to SFDC and is used when a match request is sent to D&B.

After a primary address is determined, the address goes through a following series of checks:
  1. Address completeness to check if the primary address has all the address attributes. For example, if the State Code and Zip attributes are missing, then chances of sending this record for matching to D&B is very low. Incomplete primary addresses are rejected.
  2. Reject primary addresses that are not verified.
  3. Select primary addresses received from a specific source.

If the primary address does not pass the above-mentioned checks, the Get Match button displays an error message mentioning Organization attribute address is absent.