The app uses the Autocomplete search type of the Experian Address Validation API for real-time validation. 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.
For passive validation in the background the app uses the Validate search type. This can be used with no user interaction required to return fully formatted addresses provided a verified match to a single deliverable address was made.
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 when using inline edit mode:
This changes slightly when the New/Edit button has been overridden and the modal window is being used:
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.
If your object contains a set of custom fields to represent an address, which are laid out across separate rows and have been configured as a Touchpoint, the fields are collapsed into a single address component in the layout which only consumes one row. This can lead to blank spaces below your address and to the right if you are using a two column page layout. A workaround for this is to stack all the fields that belong to the custom address on top of one another with blank spacer fields in the other column with the exception of the first trigger field for the address. The screenshot below demonstrates this:
When the application is updated from a previous version, we're not able to update the Page Layout used by the Custom Metadata Type as Salesforce don't allow this in managed packages. Therefore any new settings introduced in versions since the application was first installed must be manually added to the Page Layout. Settings that may be missing:
Follow these steps to add the missing setting:
If the following two fields are missing from your EDQ State Setting Object:
Follow these steps to add them: