HasAddress

The HasAddress relationship is used to link Organizations and Contacts to their corresponding addresses.

Note:
  • Depending on the implementation done in your tenant, you may or may not have HasAddress relationship type in your tenant. Use of the HasAddress relationship is deprecated in Account 360, and the relationship is disabled. Users should use the Addresses nested attribute instead.
  • All the attributes prefixed with “NCOA” are supplied by D&B. Such attributes should not be modified by the users.
Table 1. HasAddress Relationship
Property Value
URI configuration/entityTypes/HasAddress
Label HasAddress
Description  
Abstract false
StartObject configuration/entityTypes/Party
EndObject configuration/entityTypes/Location
Table 2. HasAddress Attributes
Name Attribute Type Sub-Attribute Name Data Type Description
AddressType Simple   String  
Primary Simple   Boolean  
AddressRank Simple   Int  
CareOf Simple   String  
Active Simple   Boolean  
Phone Nested Type String Type of phone number for example, Business, Home, Cell
Phone Nested Number String Telephone Number
Phone Nested Extension String Telephone Number Extension
Phone Nested Rank Int Telephone number rank. Can be used when there is more than one telephone number and they need to be ranked.
Phone Nested Active Boolean Status of the telephone number Active or Inactive.
SourceCD Simple   String  
NCOAMoveEffectiveDate Simple   Date YYYYMM (exp.: 200703): If populated, record is positive or near (Nixie) match to record(s) on NCOALINK. If you received address correction information from your customer more recent than the date in this field, ignore the NCOA information. NCOALINK will not append firm or individual name when updating customer files, retain existing firm or individual name, as well as internal information: titles, "Attention" lines, mailstops, and so on are not carried by NCOALINK or USPS.
NCOANIXIEA Simple   String A = Positive match to NCOALINK: your record has moved, and a new address has been supplied.
NCOANIXIEB Simple   String Footnote codes explain specific reasons for positive and non-positive matches.
NCOANIXIEC Simple   String Second byte of two-byte NCOALINK footnote code.
NCOAPrimaryAddress Simple   String Concatenated Primary Address. This field is a concatenation of all primary level street information: Best Primary_Number + Best Pre-Directional + Best Street_Name + Best Street_Suffix + Best Post_Directional
NCOASecondaryAddress Simple   String Concatenated Secondary Address. This field is a concatenation of all secondary level street information: Best Unit_Designator + Best Secondary_Number.
NCOAPriNumChangeIndicator Simple   String Field has been modified from its input value through the Cleanse process Y: Yes
NCOAPreDirChangeIndicator Simple   String Field has been modified from its input value through the Cleanse process Y: Yes.
NCOAPriNameChangeIndicator Simple   String Field has been modified from its input value through the Cleanse process Y: Yes
NCOASuffixChangeIndicator Simple   String

Field has been modified from its input value through the Cleanse process

Y: Yes.

NCOAPostDirChangeIndicator Simple   String Field has been modified from its input value through the Cleanse process Y: Yes.
NCOASecUnitDesChangeIndicator Simple   String Field has been modified from its input value through the Cleanse process Y: Yes.
NCOASecNumChangeIndicator Simple   String Field has been modified from its input value through the Cleanse process Y: Yes.
NCOACityNameChangeIndicator Simple   String Y = Yes. Field has been modified from its input value. N = No change in field i.e. Data Cleansing did not make any correction to this field.
NCOAStateAbrevChangeIndicator Simple   String Field has been modified from its input value through the Cleanse process Y: Yes.
NCOAZIPCodeChangeIndicator Simple   String Field has been modified from its input value through the Cleanse process Y: Yes.
NCOAZIP4ChangeIndicator Simple   String Field has been modified from its input value through the Cleanse process Y: Yes.