DQE One Field Reference in Dynamics

Unlike the DQE One package for Salesforce, the Dynamics package does not create fields the first time you run a check — every dqe_* field below ships with the managed solution as soon as it's imported, on Account, Contact and Lead only. A field exists whether or not its feature is enabled and whether or not it's placed on a form — enabling a feature in Configure address, email, phone and B2B validation in Dynamics only turns on validation, it doesn't add or remove columns.

This article covers two separate things, and the fields they create are different:

• Real-time validation (Address, Phone, Email, Name, B2B) — the package's own PCF controls, validating as you type or on save. Covered first below. These fields ship statically.
• Batch processing (Check Email, Check Phone, Check Postal Address, Check B2B, and Unify/deduplication) — these aren't a feature of the Dynamics package at all. They only exist if you connect your Dynamics environment to DQE One Standalone as a data source and run a process against it there. Covered in its own section near the end, since the fields it creates are Standalone's, not the package's.

Address

Address has no custom field beyond a country lookup for each address slot — there's no persisted "last validation result" field out of the box. Note that address has two separate, independently toggled sub-features: live-typing autocomplete and an on-save check (RNVP-style) — enabling one does not enable the other.

Address 3 only exists on Contact, which has a third native address block that Account and Lead don't have.

Phone

Like Address, Phone has no persisted validation-result field — only a country lookup per phone number, including the phone numbers embedded inside each address block.

Total: 9 phone-country fields on Account, 13 on Contact, 10 on Lead.

Email

Email has no dedicated custom field at all — it validates directly against the native emailaddress1, emailaddress2 and emailaddress3 fields. If "Suggest Last Name and First Name" is enabled in the settings, a matched email can also suggest values for the native firstname/lastname fields — again no custom field is involved.

Name

Name also has no dedicated custom field. Gender detection is optional and off by default: when configured through the field-mapping tool (see below), it writes to Dynamics' own native gendercode choice field, not a dqe_* field.

B2B (Account only)

B2B fields only exist on Account. Out of the box, only dqe_lib_nace is placed on the form and mapped by default — the others are inert until an administrator adds them to the form and maps them through the field-mapping tool.

A sixth field, dqe_siretcheckcontrol, exists on Account but is literally labelled "[LEGACY] dqe_siretcheckcontrol" in the app — it isn't used by anything and can be ignored.

dqe_leadsource also exists, identically, on Contact.

Batch processing fields (via DQE One Standalone)

Connect your Dynamics environment to DQE One Standalone as a data source, and you can also run Check Email, Check Phone, Check Postal Address, Check B2B, or a Unify (deduplication) process against your Dynamics records as a batch job — distinct from, and in addition to, the real-time validation above. Deduplication specifically is only available this way: Dynamics itself has no dedup fields or engine of its own (confirmed absent on Account/Contact/Lead) — the externally-hosted DQE One Standalone application is what runs it (see DQE for Microsoft Dynamics — Overview for how it connects).

The fields these batch processes create use Standalone's own naming convention, always lowercase on Dynamics (e.g. dqe_mobilephone_qc__c), and are separate from — and can coexist with — the real-time fields documented above (so, for example, a Phone field checked both ways would have a dqe_telephone1countrycode field from the package and a dqe_telephone1_qc__c-style field from Standalone). For the full field list per process kind, see Field Reference in DQE One Standalone.

Where field mappings and settings live

There's no single config record equivalent to the Salesforce package's mapping object. Two separate places hold configuration:

• DQE Paramétrages DataQ (one settings record per environment) — the per-feature enable toggles, which address/email/ phone slots are shown per entity, the default country, and the DQE One Standalone URL. Covered in Configure address, email, phone and B2B validation in Dynamics.
• The field-mapping tool (opened from the settings record) — only used today for two things: the optional gender mapping (Name) and the B2B enrichment mapping (around 65 possible source fields, covered in the same article above).

Known quirks and limitations

Two forms use the wrong country field for address validation. On the Account form's Address 2 block and the Lead form's Address 1 block, the address control is wired to a phone country-code field instead of the matching address country-code field — the City/Postal Code controls on the same blocks are correctly wired. In practice, address validation on these two specific blocks may use the wrong country. This has been reported internally; if you rely on either of these two blocks, ask DQE Support to confirm the status for your installed version.

• No validation-result field is persisted out of the box for Address or Phone — only the country lookup exists. If you need to know whether a record passed validation, you'll need to add your own tracking field and populate it from the PCF control's optional output (not configured on any shipped form).
• On Lead, the three phone country-code fields' English labels read "Phone Business Phone: Country Code", "Phone Home Phone: Country Code" and "Phone Other Phone: Country Code" — the duplicated word is a labelling quirk, not a sign the field is wrong.
• On the settings record, the field holding your DQE One Standalone URL has no English label (French orgs see "URL de Standalone"; English orgs see a blank label next to the same field) — look for the field right after "DQE Licence" if you can't find it by name.

Related articles

• DQE for Microsoft Dynamics — Overview
• Configure address, email, phone and B2B validation in Dynamics
• DQE One Roles and Permissions in Dynamics
• Field Reference in DQE One Standalone