TABLE OF CONTENTS

• Identification of Table and Field Mapping Parameters
• Selection of address fields
• Configure Dataverse Workflow Process to validate an address

Identification of Table and Field Mapping Parameters

• In the navigation bar, go to Address Validation -> Settings -> Field Mappings.
• Create a new record and enter the following information:

• Configuration Name: Unique name of the configuration record (e.g. account-billingaddress)
• Table Name: Schema name of the source Table (e.g. account).
• API Configuration : This is a lookup to select the Address Validation API Key that will be used to run the background process against the table for which the field mapping is being created.
• Overwrite existing address with verified address: Yes or No. 
  • When set to Yes, you will get to pick on set of addresses that will be used as input and output, this means the process will read the values from these fields, process them with the address validation API and overwrite their values with the result. 
  • When set to No, you'll have to pick a set of fields for input address and a different set of fields for the output (i.e. we will read from input, and write the validated address to the output). This is often used to preserve the data entered by users when Dataverse Auditing is disabled.

Selection of address fields

Once the General information is completed, you must fill out the information in the Address fields. 

• Only fields of type text are allowed for all address fields except for Latitude and Longitude, which require a Floating Point Number.

Configure Dataverse Workflow Process to validate an address 

Once you have created a field mapping record, you can create a workflow that will leverage the mapping to verify your addresses. 

• Start by navigating to your Power Apps Maker portal
• Go the Solutions area and pick the solution where you want your workflow to be included
• Click on New -> Automation -> Process -> Workflow to create  your workflow.

• On the next window, select the table where the address to validate is located, and type in a name for your workflow and click on the Create button at the bottom of the window.

• After you have created the Workflow, click on "Add Step" and in the "Address Validation" menu, you will see a custom step named "Verify Address"

• Type a description for the Step (e.g. “Validate Account Address 1”). 
• Click on Set Properties
  • The parameters are both optional in the user interface, but one of them is required to function. If both are provided, the lookup will be used first. If none is provided, the workflow will return an error. 
  • You can provided the Configuration Name : this is the name of the Field Mapping Configuration record (see previous section of this article document in the General tab of the Field Mapping record OR
  • Select the lookup of the Field Mapping record (Field Mapping Configuration property) 
  • Note that only one of the parameters is needed. 

• The custom workflow does the following operations when it runs
  • It reads the input parameters from the Field Mapping record. 
  • It processes the address validation using the configured address verification API.
  • It returns the verified address component as output parameters giving administrators the ability to configure the application behavior in a way that meet their needs. 
  • It does not write the verified address to the destination fields. 
  • The example below shows how the verified address fields are written the Account's description field.

• The following table shows the list of columns returned by the custom workflow step

As a reference, we are using the following address to show examples in the table below : 

175 W Jackson Blvd, Ste 500

Chicago, Cook County, IL 60604-3024

United States of America