Address autocomplete, email/phone validation, company (B2B) suggestions and name validation all call DQE webservices through Dynamics Custom APIs. When something is misconfigured, these features typically do not show an error message on the form — they just stop returning suggestions, as if nothing happened. This article explains the real, most common causes and where to find the exact reason.
Common symptoms
- No address suggestions appear while typing in an address field.
- The RNVP address-check comparison does not appear when saving a record, or silently skips one address block.
- Phone, email, company or name lookups never return any result.
- Nothing is displayed on the form itself to explain why — no banner, no error notification.
Why nothing shows on the form
These features are designed to fail quietly: if the underlying Custom API call returns an error, the PCF control or the address-validation dialog simply discards it and shows no suggestions, rather than interrupting the user with an error popup. The real reason is written to two places instead:
- The environment's Plug-in Trace Log — always, for every field (address, email, phone, name, company).
- The browser console (F12 → Console) — in addition, specifically for the address-check comparison shown when saving a record.
Enabling and reading the Plug-in Trace Log
- Open the Power Platform admin center, go to Manage → Environments, and select the target environment.
- Click Settings → Resources → All legacy settings to open the classic Settings area.
- If trace logging isn't already enabled, go to Settings → Administration → System Settings, open the Customization tab, and set Enable logging to plug-in trace log to Exception or All.
- Reproduce the issue (type in the field, or save the record), then go to Settings → Customization → Plug-in Trace Log and open the most recent entry for the DQE Custom API you're testing. The message will contain one of the exact messages below.
Note: the exact wording in the trace log depends on the Dynamics UI language of the user who triggered the action. DQE only has translations for English, French and Spanish. In any other UI language (German included), every one of these errors is logged using the same generic fallback text instead of the specific message below — in that case, temporarily switch your personal language to English, French or Spanish (Settings → Personalization Settings → Languages) to see which one it actually is, or test the causes in the table below one by one.
What each message means
| Message you'll find in the trace log | What it means | Where to fix it |
|---|---|---|
| "The 'DQE Setup DataQ' record could not be found. Please create it to proceed with the operation." | No DQE DataQ Settings record exists yet in this environment (the message uses an older internal name, "DQE Setup DataQ" — it refers to the same record). | Complete DQE DataQ Settings as described in DQE One Package Setup §2. |
| "The license is missing from the 'DQE Setup DataQ' configuration. Please provide it to proceed." | The DataQ Settings record exists, but its DQE Licence field is empty. | DQE DataQ Settings → General → DQE Licence (Package Setup §2.2). |
| "Invalid license. Please check your license key." | A licence key is set, but the DQE licence server rejected it — usually a wrong, expired or mistyped key, or an Org ID the key isn't authorized for. | Double-check the key against the one provided by your DQE project manager; contact them if it still fails. |
| "Missing DQE Address API URL" | The Adresse de l'API DQE field in DataQ Settings is empty. | DQE DataQ Settings → General → Adresse de l'API DQE (Package Setup §2.3). |
| "ISO3 Country is missing" | DQE couldn't resolve an ISO3 country code for the record — see below. | See Country not resolving below. |
Country not resolving ("ISO3 Country is missing")
Before calling the DQE webservice, DQE first resolves an ISO3 country code for the record: it looks at the record's own country field (via the DQE country table), and if that doesn't resolve, it falls back to the Address Default Country field configured in DataQ Settings. The error only appears when both lookups fail. Check, in this order:
- The record's own country field has a value, and that value exists in the DQE country table with a valid ISO3 code.
- If the record's country field is empty or unmapped, that DQE DataQ Settings → Address Default Country is set to a valid entry.
When to contact DQE Support
If the Plug-in Trace Log shows none of the messages above, or shows a generic "An error occurred during plugin execution" message, the cause is outside DQE's own configuration checks (for example, a network or DQE server-side issue). Share the exact trace log entry with your DQE project manager.
Related articles
- DQE One Package Setup on PowerApps / Dynamics
- Configure address, email, phone, name and B2B validation in Dynamics
Related to