Microsoft D365 uses the Autocomplete search type of the Experian Address Validation API. Our Autocomplete search type is designed to provide accurate suggestions in real-time, that continually update as the user types. The user should provide the address elements in the order that they would appear on an envelope.
If you are getting a component error, it is normally due to something going wrong in the set up of the app configuration (typically when creating the Named Credentials). Try the following things to rectify this error:
Server side errors can be found in the EDQ Error Logs item:
In addition, we also log some errors on the frontend, which can be viewed in your browser's Developer Console. Here's an example at the ERROR level:
We also log at the INFO and WARN levels, such as in the case of unlicensed or missing Enrichment attributes.
Default frontend log level is ERROR
The default country setting should be applied with the following priority order:
A bug exists which means the order is currently:
The workaround is to set the value you require in LEDQ Settings, but the bug will be addressed in a future release.
Inline editing is not available on non-EDQ Lightning components when the Edit action is overridden. This is an intentional Salesforce behavior and also happens with the standard Salesforce Record Detail component. One possible workaround is to remove the override for Edit only and rely on inline editing on the Lightning record page. Then, the Edit button should be removed from the page layout, as it will trigger the non-EDQ editing flow.
The number of suggestions is controlled by the Max Address Picklist Suggestions setting which is detailed on the Configure global settings page. The value is configurable from 1-25, with the default value being 7. Note that we do not recommend going above the default, as this may impact response speed.