Phone mapping

Mapping allows you to map a collection of data values returned by the Experian Phone 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 phone data too, assuming the additional phone data has been enabled and the fields created as detailed in the previous sections of this guide.

Configuring a phone mapping

First select an existing mapping or add a new one:

1. Go to the Experian Data Validation Configuration Power App.
2. Select the Map fields page from the left menu.
3. From the entities list on the left select the entity for which you want to configure an address mapping.
4. Either select an existing mapping from the list in the MAPPINGS column or click + Add in the top menu to create a new mapping.
5. If adding a new mapping, select the Entity name, provide a Mapping name and then click Add.

The properties from our Phone Validation API are found under the Phone data fields tab, but will only appear if enabled on the Additional data page under the Phone result or Phone metadata sections.

The process for mapping the fields is as follows:

1. 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.
2. For any standard or additional address data fields that you want to ignore, choose the value Not mapped from the combo box.

Additional form field configuration

If you have configured a mapping for additional phone data as detailed above you will need to associate the mapping with the phone field on the form.

1. Go to Customize the System.
2. Expand Entities in the left panel.
3. Expand the entity you want to configure (e.g. Account) and click Forms under the chosen entity.
4. Click the form you want to configure (e.g. Account Quick Create). This will open a new window.
5. Select the phone field you would like to configure.
6. Select Change Properties from the ribbon and go to the Controls tab.
7. Select the EDQPhone control.
8. Click the pencil icon by Mapping name.
9. 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 country calling code and validation tracking values there are some extra steps:

1. Click the pencil icon by Country code field.
2. Under Bind to a value on a field select the field created for the country calling code.
3. Click OK.
4. Click the pencil icon by Validation message.
5. Under Bind to a value on a field select the field created for the Phone Validation message.
6. Click OK.
7. Click the pencil icon by Validation timestamp.
8. Under Bind to a value on a field select the field created for the Phone Validation timestamp.
9. Click OK.

Once all the steps have been completed click OK to close the Field Properties dialog box and repeat for other phone fields as required.