Address components

If you're using the EDQ Record Detail component to validate addresses, it's possible to make use of the Components object which is also returned from our Experian Address Validation API. The Components object contains all the available components which make up the address. This is enabled through configuration of Touchpoints.

Setting up Touchpoints to return address components

1. Click on App Launcher. Type EDQ Global Settings in the Quick Find box, and select it.

2. Select Touchpoints from the left-hand menu.

3. Click the New button found in the top right to create a new Touchpoint configuration for your Salesforce object.

4. Choose whether you want to create a Touchpoint for a Standard address field (including the new Custom Address Field) or a set of Custom fields used to represent an address:

   • For standard address fields you just need to choose the object and then select from the list of dynamically generated address fields found within that object.
   • For custom fields you can refer to the additional instructions on configuring address Touchpoints with custom fields to understand how these are configured.

5. Activate the optional Passive validation feature should you wish to use it.

   

With your address configured you can now decide which components you want to retrieve and which fields on your object you want this to be mapped to. This data is unique to each country, so a set of mappings must be created for each country you require.

6. Under the Country-level mapping heading click the New mapping set button.

7. On the Country level mappings page select your country and the Components mappings section will appear below, allowing you to then click the New component mapping button.

   

   You can now create as many mappings as you require. For each mapping you first select from the list of possible components from our API and then select a field from the Salesforce object chosen for your Touchpoint. For a full list of components and their descriptions refer to our Address Validation API Components documentation.

   Country specific components

   Note that components vary slightly from country to country. Components that do not contain any values for the selected address will not be returned by the API. The full list of components with details for our most popular countries plus a rest of world column for all other supported countries can be found in our Address Validation API Components documentation.

   Unwanted mappings can be removed using the cross icon to the right of the mapping and further new ones added using the New component mapping button.

   Unmapping fields which have already been populated

   If a field mapped in a Touchpoint has been populated and is subsequently unmapped, the field values for the records that have already been populated will need to be cleared manually. Otherwise, there is the possibility that the value in the field is associated with an address returned from a subsequent address validation.

8. Once all the mappings have been configured, click the Add country mappings button to add the set of mappings for that country.

9. Repeat this process for other countries as required and then click Save to save your Touchpoint configuration.

   Remember to save the Touchpoint

   Once you've made any changes to the country mappings and returned to the Touchpoint configuration page, you must remember to save the overall Touchpoint to commit the mapping changes.

Testing your Touchpoint mappings

1. Make sure all the fields that were mapped in your Touchpoint have been added to the Page Layout for the relevant Salesforce object.
2. Edit a record for the Salesforce object you want to test and try to validate an address using an EDQ component.
3. If the validation is successful, check that the mapped fields are populated with the additional data you were expecting.

Handling of missing components

If you mapped an attribute which doesn't exist for the validated address, the mapped object field won't be populated when an address is returned following validation.

To make this visible to administrators for debugging purposes we utilize our package's frontend logging which appears in your browser's Developer Console. Errors will be logged at the following levels.

• INFO level when an attribute is missing for the validated address