While the solution is preconfigured to use specific fields for all kinds of validation, it is possible for these settings to be changed. All the preconfigured fields are managed through the solution’s Mapping tab. When you first get the MS Dynamics 365 solution an example mapping exists. If you do not create your own custom mapping, then the example preconfigured mapping is used.

Latitude, Longitude and Match level fields are shown if Geocoding (global datasets) is checked in the Select components tab. These components are used when a custom dataset is not specified for the request being sent.

For example, if a GBR address is searched and a custom regional dataset has been specified, fields used to store the data will be those which names start with Enrichment_. If a USA address is searched and there is no custom dataset specified for USA, then Latitude, Longitude and Match level mapped fields will be used. So, the typical settings for such a situation would be to map both Latitude and Enrichment_latitude to same field, for example address1_latitude.

To map the fields to your forms:

  1. Go to the Configuration page.
  2. Click the Map fields tab and select the entity you want your address validation mapping to appear in.
  3. Next select your chosen mapping:
    • For all standard entities and fields there will already be preinstalled mapping, click 'Address 1' or 'Address 2'.
    • Click ADD to create a new mapping (keep the name to less than 40 characters).
  4. Map the fields where you want each bit of information returning from the API to appear. If you do not want to use a field, select "Not mapped".
    • You need to have at least one trigger for the API to work.
  5. In the Address Validation column, map the corresponding validation message field and validation timestamp field you created earlier to where you want the information returning from the API to appear.
  6. Under the Enrichment components column, map the latitude, longitude and Match level fields where you want each bit of information returning from the API to appear (If you do not want to use a field, select "Not mapped").
  7. There are additional address validation components in the Additional Components column to the right, which are all optional.

To bind the fields to your forms:

  1. Go to the Customize the system.
  2. Expand Entities in the left panel.
  3. Expand your chosen entity you want to add the fields to (e.g. Account) and click Forms under the chosen entity.
  4. Click your chosen form you want to add a field to (e.g. Account Quick Create). This will open a new window.
  5. Select the field you need to map.
  6. Click Change Properties, and go to the Controls tab.
  7. Click Add Control….
  8. Scroll and select EDQAddress, and click Add.
  9. Select where you want the control tobe enabled - Web, Phone and/or Tablet.
  10. Click the pencil icon by Mapping name.
  11. Select Bind to a static value and in the text box enter the Mappings name (e.g. Address1) from the Map fields tab in the configuration page.
  12. Click OK.
  13. Repeat steps 5-12 for each field you want mapped using the custom mapping you created in the configuration page.
Microsoft Dynamics 365 PCF control

Create mappings and bind