Which EDQ components are supported?
If you're using the EDQ Record Detail component to validate addresses, it's possible to make use of the Metadata object which is also returned from our Experian Address Validation API. The Metadata object contains additional information about the returned address, such as deliverability indicators. This is enabled through configuration of Touchpoints.
With your address configured you can now decide which metadata elements 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.
Under the Country-level mapping heading click the New mapping set button.
On the Country level mappings page select your country and the Metadata mappings section will appear below, allowing you to then click the New metadata mapping button.
You can now create as many mappings as you require. For each mapping you first select from the list of possible metadata elements from our API and then select a field from the Salesforce object chosen for your Touchpoint. For a full list of attributes and their descriptions refer to our Address Validation API Metadata documentation.
Country specific metadata elements
Unwanted mappings can be removed using the cross icon to the right of the mapping and further new ones added using the New metadata mapping button.
Once all the mappings have been configured, click the Add country mappings button to add the set of mappings for that country.
Repeat this process for other countries as required and then click Save to save your Touchpoint configuration.
Remember to save the Touchpoint
Mapped fields must be modifiable
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.
Default frontend log level is ERROR