Mapping Input Attribute

Learn about the input mapping between a Reltio attribute and its corresponding cleanse attribute.

This table shows the input mapping between data model attributes in your Reltio tenant and their corresponding attributes the address cleanser returns from your source system.

Table 1. Input Attribute Mapping
Reltio Attribute	Cleanse Attribute
`AddressLine1`	`Address1`
`AddressLine2`	`Address2`
`Country`	`Country`
`SuperAdministrativeArea`	`SuperAdministrativeArea`
`StateProvince`	`AdministrativeArea`
`SubAdministrativeArea`	`SubAdministrativeArea`
`City`	`Locality`
`Neighborhood`	`DependentLocality`
`DoubleDependentLocality`	`DoubleDependentLocality`
`Street`	`Thoroughfare`
`Premise`	`Premise`
`DependentThoroughfare`	`DependentThoroughfare`
`Building`	`Building`
`SubBuilding`	`SubBuilding`
`Zip5`	`PostalCode`
`PostalCode`	`PostalCode`
`POBox`	`PostBox`
`Organization`	`Organization`

Guidelines for mapping input address data

The complexity of address structure often varies by region and available reference data, and it may also contain structural variations. This may make it difficult for you to consistently predict which specific input fields and line break positions you need to provide the necessary input format for each country.

To help avoid this challenge, we recommend that you map the input address data using only address line fields (Address1, Address2, ..., Address8) to specify input address line data. This method is preferred over using individual address input fields to specify a line-by-line construction of the address. If you enter the address line data correctly, the output will contain the correctly formatted address split into individual address lines for mailing in the relevant country.

We recommend mapping the input address data as shown in the following example:

Address lines input: (Address1, Address2, Address3 OR Address) + Country
Address lines + geographical input: Address1, Address2, Address3 + Locality + AdministrativeArea + PostalCode + Country

Note: If you have provided some of the addressinput values as separate fields (example, Thoroughfare/Premise) that are entered on separate lines, you may receive an unexpected outcome as this is not in a recommended input format. For example, Premise+Address1+Locality+Postalcode+country.

Sample Input Mapping

[
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/AddressLine1",
	  "mandatory": true,
	  "allValues": false,
	  "cleanseAttribute": "Address1"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/AddressLine2",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "Address2"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/Country",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "Country"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/SuperAdministrativeArea",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "SuperAdministrativeArea"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/StateProvince",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "AdministrativeArea"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/SubAdministrativeArea",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "SubAdministrativeArea"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/City",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "Locality"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/Neighborhood",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "DependentLocality"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/DoubleDependentLocality",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "DoubleDependentLocality"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/Street",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "Thoroughfare"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/Premise",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "Premise"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/DependentThoroughfare",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "DependentThoroughfare"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/Building",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "Building"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/SubBuilding",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "SubBuilding"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/Zip5",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "PostalCode"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/PostalCode",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "PostalCode"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/POBox",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "PostBox"
	},
	{
	  "attribute": "configuration/entityTypes/HCP/attributes/Address/attributes/Organization",
	  "mandatory": false,
	  "allValues": false,
	  "cleanseAttribute": "Organization"
	}
  ]

Unify and manage your data

Mapping Input Attribute

Guidelines for mapping input address data

Sample Input Mapping

Footer