Mapping allows you to map a collection of data values returned by the Experian Email Validation API to a collection of Microsoft Dynamics entity fields.
The pre-configured mappings that come with the solution (Address1 and Address2) are designed just for addresses out of the box but can optionally be utilized for mapping email data too, assuming the additional email data has been enabled and the fields created as detailed in the previous sections of this guide.
Configuring an email mapping
First select an existing mapping or add a new one:
Go to the Experian Data Validation Configuration Power App.
Select the Map fields page from the left menu.
From the entities list on the left select the entity for which you want to configure an address mapping.
Either select an existing mapping from the list in the MAPPINGS column or click + Add in the top menu to create a new mapping.
If adding a new mapping, select the Entity name, provide a Mapping name and then click Add.
The properties from our Email Validation API are found under the Email data fields tab, but will only appear if enabled on the Additional data page under the Email result or Email metadata sections.
The process for mapping the fields is as follows:
Under each API property is a combo box that contains the fields of the associated entity. Click on each combo box and select the field that you want populated with that API value. The list is separated into five types for convenience, depending on the data type of the field:
Text - the text value returned by the API is stored in the field.
Number - the integer or decimal value returned by the API is stored in the field. If the entity field only holds integers and a decimal value is returned by the API, the value will be truncated to an integer value.
DateTime - the date and time value returned by the API is stored in the field.
Choice - the item selected for the choice field will be the one where the text of the choice item matches the text returned by the API using a case insensitive match.
Lookup - the lookup record selected for the field will be the one where the text of the primary name column of the Lookup entity matches the text returned by the API using a case insensitive match.
For any standard or additional address data fields that you want to ignore, choose the value Not mapped from the combo box.
Choice and Lookup fields
If you map to a Choice or Lookup field without additional configuration, an empty value will be saved to the mapped field if a match is not found amongst the Choice or Lookup values.
Be careful when populated fields are unmapped
If a form field mapped in an email mapping has been used to populate entity records and is subsequently unmapped from the mapping, the field values for the records that have already been populated will need to be cleared. Otherwise, there is the possibility that the value in the field is associated with an email address returned from a subsequent email validation.
Looking to make configuration changes using the Classic interface?
If you have configured a mapping for additional email data as detailed above you will need to associate the mapping with the email field on the form.
Go to Customize the System.
Expand Entities in the left panel.
Expand the entity you want to configure (e.g. Account) and click Forms under the chosen entity.
Click the form you want to configure (e.g. Account Quick Create). This will open a new window.
Select the email field you would like to configure.
Select Change Properties from the ribbon and go to the Controls tab.
Select the EDQEmail control.
Click the pencil icon by Mapping name.
Select Bind to a static value and in the text box enter the Mapping name. This would be Address1 or Address2 if you're using the mappings that come pre-configured with the solution. Otherwise enter the new mapping name you created above.
At this point, if you want to store the optional validation tracking values there are some extra steps: