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.

  • Installing for the first time? Follow our download instructions.
  • Upgrading from a previous version? Follow our upgrade instructions.

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:

  1. Check your app configuration settings or check the Default Scope/Scope fields are correct.
  2. Try to manually type the scope in for both the auth provider and named credential sections rather than use the autocomplete value.
  3. Make sure you have copied the Callback URL correctly (only copy the URL to the first / after the domain).
  4. If none of the above work, then go through the steps again from Create a Connected app to Create a Named Credential.

Server side errors can be found in the EDQ Error Logs item:

  1. Go to App Launcher and in the search box type EDQ Error Logs, and select it.
  2. Click an individual log to view details of the error.

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:

Frontend Console Logging

We also log at the INFO and WARN levels, such as in the case of unlicensed or missing Enrichment attributes.

The default country setting should be applied with the following priority order when using inline edit mode:

  1. User setting: Found under My Personal Information > Personal Information > Country (the app will try to match the value against our LEDQ Country objects)
  2. Component setting
  3. Org setting: Found under Setup > Custom Metadata Types > LEDQ Settings > Default Country

This changes slightly when the New/Edit button has been overridden and the modal window is being used:

  1. User setting
  2. Org setting

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:

Suggested page layout to avoid blank spaces around custom address

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:

  • Enable phone code plus signs introduced in v1.10.0
  • Country picklist position introduced in v1.13.0
  • Phone Validation Supplementary Live Status introduced in v1.14.0
  • Always show EDQ statuses introduced in v1.14.0 - should be defaulted to Enabled
  • Allow country-only addresses introduced in v1.16.0 - should be defaulted to Disabled
  • Line Endings introduced in v1.18.0 - should be defaulted to Unchanged (Leave markup as-is)
  • Use formatted phone number introduced in v1.20.0 - should be defaulted to Disabled
  • Phone number output format introduced in v1.20.0

Follow these steps to add the missing setting:

  1. Go to Setup and then search for Custom Metadata Types.
  2. Click the LEDQ Settings Label (not Manage Records) and scroll down to Page Layouts at the bottom.
  3. Click Edit next to LEDQ_Settings Layout.
  4. Drag the required setting from the Fields at the top into the Information section of the page.
  5. Click Save and you'll be returned to the Detail page.
  6. Click Manage LEDQ Settings at the top of the page.
  7. Click Edit next to Configuration.
  8. You can then edit the new setting as needed.

If the following two fields are missing from your EDQ State Setting Object:

  • Three letter ISO Country Code
  • Salesforce State Name

Follow these steps to add them:

  1. Go to Setup and then Object Manager.
  2. Click on the EDQ State Setting object.
  3. Click on Page Layouts and select your layout.
  4. Drag the Three letter ISO Country Code and Salesforce State Name fields from the Fields at the top into the Information section of the page.
  5. Click Save.
  6. Once the browser is refreshed, these two fields should now be displayed for the EDQ State Setting Object.

If you want to control whether Address, Email or Phone validation is enabled and whether the EDQ validation status is displayed against a field please refer to the Enable profiles page.