Validate Addresses with Power Automate: Melissa Global Address (Unbound Action)

Overview

Address Validation for Dataverse exposes Melissa Global services (Global Address, Global Phone, Global Email and Global Name) as a Dataverse action named sharpxrm_GlobalPersonator (display name Sharp XRM - Global Personator). Power Automate can call it with the standard Microsoft Dataverse connector and its Perform an unbound action step. This article covers Global Address verification.

Like Melissa Personator, this action works on a row, not on an address you pass in. You send it the Target row and a Field Mapping. The action reads the address columns defined in the Field Mapping, calls Melissa Global Address Verification, and updates the row itself with the verified address (and coordinates and other values, if they are mapped). Your flow does not map outputs to columns. It triggers the validation and can react to the returned result codes.

Before you start

• Address Validation for Dataverse is installed, with a valid license.
• An active API Configuration row with Validation Service Type = Melissa Global and your Melissa license key. See Setup your Melissa API Key.
• An active Field Mapping row for the table (for example Table Name = contact) whose Api Configuration Record is the Melissa Global configuration, with Global Service Type including Global Address. The Field Mapping defines:
  • the address columns used as input (Line 1 to 3, unit, city, state/province, county, postal code, country) and, optionally, last name and company name,
  • Overwrite existing data with verified data: Yes writes results back into the same columns. No writes them into the destination columns,
  • Global Address options such as geocoding output, output script and US standardization,
  • Additional Mappings for extra outputs (for example the result codes in a Validation Result column).
  See Configure Background Address Validation: Field Mapping and Workflows.
• A Microsoft Dataverse connection in Power Automate.

How the example flow works

1. When a row is selected (Contacts): users run the flow from the Flow menu on a contact.
2. Contact ID (Compose): the selected contact's ID.
3. Get Global Address field mapping (List rows): finds the contact Field Mapping that uses Melissa Global with the Global Address service.
4. Field mapping found (Condition): stops with a clear error if there is none.
5. Validate with Melissa Global (Perform an unbound action): verifies and updates the contact.
6. Validation summary (Compose): turns the result codes into readable flags.
7. Melissa reported a failure (Condition): marks the run as failed when Melissa reports a failure.

Find the Global Address Field Mapping

A table often has several Melissa Global Field Mappings, for example one each for address, phone, email and name. Always pass the ID of the Global Address mapping. Otherwise the action picks a Melissa Global mapping for the table on its own, and it might not be the address one. The example uses List rows on Field Mappings with this Fetch Xml Query:

<fetch top='1'><entity name='sharpxrm_addressvalidationfieldsconfig'><attribute name='sharpxrm_addressvalidationfieldsconfigid'/><filter><condition attribute='sharpxrm_entityname' operator='eq' value='contact'/><condition attribute='statecode' operator='eq' value='0'/><condition attribute='sharpxrm_global_servicetypes' operator='contain-values'><value>229000000</value></condition></filter><link-entity name='sharpxrm_sharpxrmconfiguration' from='sharpxrm_sharpxrmconfigurationid' to='sharpxrm_apiconfigurationrecord' alias='cfg'><attribute name='sharpxrm_name'/><filter><condition attribute='sharpxrm_validationservicetype' operator='eq' value='229000000'/><condition attribute='statecode' operator='eq' value='0'/></filter></link-entity></entity></fetch>

In this query, sharpxrm_global_servicetypes contain-values 229000000 selects mappings that include Global Address, and sharpxrm_validationservicetype = 229000000 selects API Configurations of type Melissa Global.

Call the action

Add Microsoft Dataverse > Perform an unbound action and choose Action Name = sharpxrm_GlobalPersonator. Add the inputs from Advanced parameters. The designer shows "Showing 2 of 93" because the Field Mapping input lists every Field Mapping column. Only the ID field needs a value.

Input fields

Output values

Each output is prefixed with the Global service that produced it. This lets a single Field Mapping run several services, for example Address: or Phone:.

Report or react to the result

The example Validation summary compose turns the codes into flags:

• premiseLevelVerified = or(contains(ValidationResults, 'AV24'), contains(ValidationResults, 'AV25'))
• rooftopGeocode = contains(ValidationResults, 'GS05')

Common Melissa Global Address codes:

For the full list, see the Melissa result code reference on wiki.melissadata.com.

Behavior to be aware of: each Global service checks its record-level codes against the Field Mapping's Melissa Blocking Result Codes. When a listed code is returned, that service does not write its columns; the codes are still stored in the Validation Details field. When the list is empty, Global Address blocks any AE (address error) or GE (geocode error) code, and Global Email, Phone and Name write every result. A blocked address does not stop the other services from saving their results. To also refuse partially verified addresses, add AV1* to the list. If you only want premise-level data to replace the original address, you can still set Overwrite existing data with verified data to No and copy the results over in the flow when premiseLevelVerified or rooftopGeocode is true.

Expected results

• 1600 amphitheatre pkwy, mountain view, CA, USA: Address:Success, Address:AC01,AC16,AV24,GS05. The contact is updated to 1600 Amphitheatre Pkwy, Mountain View, CA 94043-1351, Santa Clara, United States of America, with coordinates. ValidationStatus is Address:VERIFIED; premiseLevelVerified and rooftopGeocode are both true.
• Main Street, Toronto: Address:Success, Address:NOT_VERIFIED, Address:AC01,AE02,AV12,GE02. The address columns are not changed and both flags are false.

Troubleshooting

Related articles

• Setup your Melissa API Key
• Configure Background Address Validation: Field Mapping and Workflows
• Address Validation using Dataverse Workflow Processes
• Validate Addresses with Power Automate: Melissa Personator (Unbound Action)