Release notes

v3.2.3 - August 2023

In this release we have a bug fix update.

New features:
No new features were included in this release.

Enhancements:
No enhancements were done for this release.

Bugs fixed:

• When validating new addresses, the fields from the previous address are no longer incorrectly retained.

v3.2.2 - November 2022

In this release we have a bug fix update.

New features:
No new features were included in this release.

Enhancements:
No enhancements were done for this release.

Bugs fixed:

• Enhanced spellcheck offered by Chrome and Edge disabled by HTML attribute to mitigate "spell-jacking" vulnerability.

v3.2.1 - June 2021

In this release we have a bug fix update.

New features:
No new features were included in this release.

Enhancements:
No enhancements were done for this release.

Bugs fixed:

• The Address Line 2 field is updated and now clears to show a new value or left blank according to the response from the Address API.

v3.2.0 - April 2021

In this release we have both bug fixes and new features.

New features:

• Experian Address Validation is now the API being called from this version of the Microsoft Dynamics 365 integration product. Please note that Global intuitive is no longer being called from v3.2 onwards.

In order to seamlessly accommodate the new API there are new settings that can be utilized during configuration:

• Map, capture and display component collections for address, as well as the metadata fields on validated country specific address data (i.e. Point of Delivery(AUS), UDPRN (UK), GNAF ID, RDI (USA)).
• All component collection fields can now be enabled for use in a new Select components tab, making it easier to select required fields and map them to Dataverse columns.
• With Experian Address Validation there are now additional UK address datasets, Multiple Residence and Not Yet Built, which are also supported in this integration product. Map these additional datasets during configuration.
• All datasets available through the Experian Enrichment API can now be easily and quickly configured and utilized within the integration. Full datasets can now be mapped i.e. Global Geocodes, UK Location Essential/ Complete, USA regional geocodes and AUS regional geocode, NZL regional geocode datasets. Any new licensed datasets and attributes can be easily added without upgrading the solution in Microsoft Dynamics 365.

Enhancements:

• Enhanced order of Triggers, Email and Phone validation fields providing a more user-friendly Configuration interface.

Bugs fixed:
No bug fixes raised for resolution.

v3.1.4 - December 2020

In this release we have a bug fix update.

Bugs fixed:

• Resolved issue with phone validation where Phone validation was only triggering on every second number input to the trigger fields.
• Resolved a Classic interface issue where the validation engine was not triggering when a customer is using Microsoft Dynamics Classic interface.
• Resolved a validation issue for the Quick Create form.

v3.1.3 - November 2020

In this release we have both bug fixes and new features added, per the below notes.

Enhancements:

• Changed dataset for Australia geocodes to use the regional datasets
• Added support for Datafusion and GNAF in combination with enrichment API
• Added GNAFID to mappings configuration

Bugs fixed:

• Trigger for Address validation not resulting in API response, only for the address fields in the non-visible part of the web page
• Address results suggestion list not hiding after clicking away from field
• Datasets selected in Configuration page not saving

v3.1.2 - September 2020

In this release we have added 10 of the United Kingdom components collections, listed below from the components available as part of the Address validation to the Mappings page.

This will allow you to map address fields using the standard 7-line Address Collection from the API or enhancing your mappings by using the 10 additional components now available.

There is no change to the Mappings process.

The 10 new elements of the United Kingdom Components collection are:

• subBuilding1
• building1
• country1
• locality1
• locality2
• locality3
• postalCode1
• street1
• street2
• streetNumber1

v3.1.1 - July 2020

• Bug functionality fixes completed

v3.1.0 - July 2020

• Faster installation and configuration
• All configuration settings are now in one place (Configuration page).
• Added custom entities and fields mapping
• New "Map fields" tab added
• All entities and their fields (standard or custom) can now be mapped to the APIs' response fields.
• For all standard entities and fields, two mappings (Address1 and Address2) are preconfigured.
• Added delivery Point ID field for Australia.
• Added Country phone code field.
• Now a custom field can be specified to hold the country code. This way only number without country code added can be validated. Each of the phone fields can have separate country code field or all of them can share one country code field.

v3.0.2 - April 2020

Different address entities can be utilized on one form, i.e. you can have address1, address2 and address3 on the same form and validation could be applied on the 3 addresses separately by adding 3 to 6 more records in "Mappings" entity.

Output phone format now works for all available formats.

v3.0.0 - February 2020

• Address, email, and phone validation integrated in one solution package
• Location Insights Enrichments, where enabled
• Intuitive user interface, with in-line, real-time validation
• All configuration settings in one place
• Fast installation and configuration
• Flexible tracking options