Recipient address – XML contact mapping
Contact data is often transferred from third-party systems, which in some cases requires contact mapping.
Note
There are two different types of contact mapping:
XML contact mapping (documented on this page)
XML contact mapping configuration have about this form:
<ContactMapping>
<ContactItemXPath>Contact</ContactItemXPath>
<ContactElement id="Person_LastName">lastNameSource</ContactElement>
</ContactMapping>
Default contact mapping (Link)
Standard contact mapping configurations have approximately this form:
<Mapping>
<Map Source="lastNameSource" Target="Person_LastName" />
</Mapping>
For these mapping types, different names must be used for the contact target fields.
Address providers that use the XML contact mapping:
Configuration:
<ContactMapping>
<!-- Default setting, see the documentation for corresponding AddressProvider in each case -->
<ContactItemXPath>Contact<//ContactItemXPath>.
<!-- Mapping of address provider date with key "PERSON_LASTNAME" (possible keys: see documentation from corresponding AddressProvider) -->
<ContactElement id="Person_LastName">PERSON_LASTNAME</ContactElement>
<!-- Mapping from defined value "FIXED VALUE" -->
<ContactElement id="Person_Title">"FIXED VALUE"</ContactElement>
<!-- Mapping of address provider date with key "STREET", but only if address provider date with key "TYPE" has content "INTERNAL ADDRESS" -->
<ContactElement id="Company_Street" when="TYPE = 'Internal Address'">STREET</ContactElement>.
</ContactMapping>
All possible contact target fields are listed below.
- Person
(All person target fields requirePerson_LastNameorPerson_FirstName.)Person_LastNamePerson_FirstNamePerson_TitlePerson_SecondNamePerson_NickNamePerson_InitialsPerson_ProfessionPerson_PositionPerson_SalutationShortPerson_SalutationPerson_Greeting- Address
Person_StreetPerson_CareOfPerson_ApartmentPerson_FloorPerson_CityPerson_ZipCodePerson_PostOfficeBoxPerson_PostOfficeBoxCityPerson_PostOfficeBoxCityZipCodePerson_CountryPerson_CountryShortCode
- Communication
Person_LanguagePerson_PhonePerson_EmailPerson_FaxPerson_MobilePerson_Homepage
- Company
Company_NameCompany_SupplementCompany_Department- Address
Company_StreetCompany_CareOfCompany_ApartmentCompany_FloorCompany_CityCompany_ZipCodeCompany_PostOfficeBoxCompany_PostOfficeBoxCityCompany_PostOfficeBoxCityZipCodeCompany_CountryCompany_CountryShortCode
- Communication
Company_LanguageCompany_MobileCompany_HomepageCompany_PhoneDirectCompany_PhoneCentralCompany_EmailDirectCompany_EmailCentralCompany_FaxDirectCompany_FaxCentral
- Options
Options_SelectedAddress(ValueBusinessorPrivate)Options_AddressingType(ValueTo,CcorBcc)Options_PersonOverFirm(Valuetrueorfalse)Options_CountryView(Valuetrueorfalse)Options_CountryCodeView(Valuetrueorfalse)Options_SalutationView(Valuetrueorfalse)Options_SalutationSeparatetLine(Valuetrueorfalse)Options_SecondNameView(Valuetrueorfalse)Options_PositionView(Valuetrueorfalse)Options_InterneAddress(Valuetrueorfalse)
- Provider
Provider_IDProvider_NameProvider_Updated(Date, e.g.2023-01-24)Provider_Published(Date, e.g.2023-01-24)Provider_AddressLabelProvider_URL
- ExtendedField
(The names of ExtendedFields can be chosen freely, the prefixDynamic.is added in each case. Below are some examples).ExtendedField_Field1(creates ExtendedFieldDynamic.Field1)ExtendedField_CustomerNumber(creates ExtendedFieldDynamic.CustomerNumber)ExtendedField_MaritalStatus(creates ExtendedFieldDynamic.MaritalStatus)
Note
The AdditionalPerson cannot be mapped to with this.