Overview
This release focuses on a more reliable, secure, and supportable address validation experience. Address autocomplete controls recover more clearly from configuration or provider errors, browser configuration refresh is more predictable, and standard users can complete licensed operations without unnecessary access to license records.
Changes are grouped first under General, followed by the affected Support API Type.
Highlights at a glance
Address autocomplete controls now show clearer errors instead of remaining in a loading state when configuration or provider requests fail.
Browser configuration caching is safer and refreshes more predictably;
Fixed two issues with there standard user security role (access to transaction logging, and no access to edit the license record).
A new in-product diagnostics page gives administrators and support staff one place to review versions, licensing visibility, access checks, recent trace logs, and an API configuration test.
Azure Maps new uses a more modern and faster framework that makes rendering faster.
General
More reliable autocomplete startup
Configuration and provider errors are now handled consistently. When a request cannot be completed, users receive an actionable error instead of seeing an indefinite loading indicator.
Safer browser storage and predictable refresh
Provider credentials used by autocomplete controls are retained only for the current browser session and are removed when the session ends.
Cached configuration entries are automatically refreshed when they expire or become invalid, reducing the need for users to clear their browser cache after an upgrade.
Google Maps, Canada Post, and Melissa Express Entry controls now offer an optional Configuration Cache Hours setting. The default is 24 hours, with supported values from 1 to 168 hours.
Permissions and license reliability
Users assigned the current SharpXRM - Address Validation User role can complete validation transaction logging without receiving permission errors. License-cache maintenance is handled by the solution and no longer depends on an end user having write access to the license record.
Administrator action: after importing this release, use the updated SharpXRM security role. Organizations that copy permissions into a custom role should compare that role with the current supplied user role.
New diagnostics experience
A new Address Validation diagnostics page helps administrators and support staff review the installed solution and plug-in versions, license visibility, current-user access, recent SharpXRM trace logs, and the result of a live API configuration test. Sensitive provider credentials are not displayed.
Azure Maps
The Azure Maps autocomplete control has moved to the current shared control framework. The control keeps the same identity and form properties, so existing form configurations continue to work without being recreated.
Configuration loading and error handling are more reliable, helping users recover when an API configuration cannot be loaded.
Google Maps
Authentication and map-loading failures now provide clearer guidance instead of leaving the control in a loading state.
The autocomplete search field has a clearer accessible name for users of assistive technology.
Canada Post
The autocomplete search field has a clearer accessible name for users of assistive technology.
Melissa Express Entry
Configuration errors are reported more clearly and cached settings refresh automatically when invalid or expired.
Melissa Personator
When Personator returns a blocking result, the mapped address fields now remain unchanged instead of being overwritten. This helps preserve the user's original data when validation cannot safely complete.
Upgrade notes
No form reconfiguration is required for the Azure Maps control upgrade.
Use the latest supplied SharpXRM security roles after importing the solution.
Browser cache clearing should not normally be required after this upgrade; configuration entries expire and refresh automatically.