FAQ
Answers to common questions about 365 business Address Validation: license, trial period, companies, countries, and how it works with other systems.
The questions cover 365 business Address Validation for Microsoft Dynamics 365 Business Central and are grouped by topic. Each answer includes a link to the full page. For messages and their solution, see Troubleshooting.
More questions
If your question is not listed here, contact our Service Desk.
General
What is the difference between address validation and address prediction?
Address validation compares an address that has already been entered against an external service and suggests a corrected or completed address when it differs. Address prediction starts before the entry is complete: while you type, it suggests matching addresses to choose from, similar to the autocomplete in a map application. An address applied through prediction also counts as validated. For more information, see Address validation and address prediction.
Is there a block on documents with an unvalidated address?
No. 365 business Address Validation does not block posting or releasing a document because an address could not be validated. In a session with a user interface, a service error triggers a prompt asking whether to continue without validation; declining only cancels the current save operation. Without a user interface, for example during an API or web service insert, no prompt appears: a service error cancels the save operation directly. On purchase documents, a service error is not shown at all, and the document is saved without validation. See Troubleshooting.
Which countries does address validation work for?
365 business Address Validation does not restrict validation to specific countries in the product itself. The Country/Region Code field is passed to the address validation service of the 365 business API unchanged; how exactly the service recognizes an address in a given country depends on that external service and is not defined by the product.
License and trial period
How long can I try 365 business Address Validation?
A 30-day trial period is available for both Address Validation and Address Prediction. After that, a subscription is required for continued use. See Get started.
What licensing models are available?
Address validation offers the Company (per company) and Tenant (per tenant or on-premises environment) licensing models; address prediction additionally offers User (per active user). Current prices are available on the Address Validation pricing page.
Do I need a separate license for every company?
It depends on the licensing model. With the Company model, you need a separate license for every company. With the Tenant model, the license covers the whole environment (the tenant or on-premises environment), including every company in it. For address prediction, the User model applies in addition, binding the license to individual users instead of a company.
Address validation
Does a known address consume a validation?
If an entered address matches an address that was already validated in the address directory, 365 business Address Validation does not call the external validation service for it again; the known address is applied unchanged. See Address directory.
Integration and third-party systems
Are orders from third-party systems or created through the API also validated?
Yes, provided the record is changed again after it was inserted: automatic validation reacts to a record being modified, not to it being inserted. If a third-party system or marketplace creates an order through the API or a web service with a complete address and never changes it afterward, no automatic validation takes place. If the service returns several possible matches in a session without a user interface, 365 business Address Validation automatically applies the best match without showing a selection page. If validation fails, the save operation is canceled without a prompt; on purchase documents such a service error is not shown, and the document is saved without validation. Affected partners can instead validate the address explicitly through the public AL surface (codeunit bdev.Address Validation API). See Troubleshooting.