This article covers creating a Unify process whose Process kind is B2B Check, Address Check, Email Check, Phone Check or Name Check — grouped under Data Quality in the Process kind picklist. For Duplicate Check and Multi-source Duplicate Check processes, see Set up Unify processes and rules instead. For day-to-day navigation once your processes exist, see Using the DQE Unify Console. For the DQE-created result fields these checks leave on your records and on their mapping, see DQE One Field Reference.
Starting a Data Quality process
Open the DQE Process tab and click New. In the Process kind field, pick your check under the Data Quality group. The general settings (name, description), the source object and the list view work the same way as for a Duplicate Check process. The Advanced Options window is structured the same way too, but its content is check-specific: Address Check adds its own Automatic RNVP Merge option, B2B Check adds Automatic B2B Merge, and Email, Phone and Name Check have no check-specific advanced option. What differs most is the Select a Data Source step, which asks for different fields depending on which check you picked.
A Mapping field is offered for every Data Quality check, letting you attach an existing DQE Mapping record:
| Process kind | Mapping required? |
|---|---|
| B2B Check | Yes |
| Address Check | No |
| Email Check | No |
| Phone Check | No |
| Name Check | No |
Regardless of the check, a Mapping is also required whenever the process reads from a Data Cloud source.
B2B Check
Once you've selected your source object, provide:
- Select a Company Name field — the field holding the company's name.
- Select a Company Number field — the field holding its SIRET/company identifier.
For the company's address, B2B Check uses the same field-selection mechanism as Address Check (below): picking a standard compound address field auto-fills the matching sub-fields, or you can choose Custom Address to map them individually.
| Field | Required to save a B2B Check process? |
|---|---|
| Mapping | Yes |
| Company Name field | Yes |
| Company Number field | Yes |
| Address fields | No |
Address Check (RNVP)
In Select a field, pick the address field group to validate. If your object has a standard compound address field (for example Account's Billing Address), selecting it auto-fills the Street field, Postal Code field, City field, State field and Country ISO-2/ISO-3 field from its own sub-fields.
To map a set of fields that isn't a single standard compound field, choose Custom Address at the bottom of the Select a field list instead. This unlocks each sub-field for manual selection:
| Field | Required? |
|---|---|
| Street field | Yes |
| Postal Code field | Yes |
| City field | Yes |
| State field | Yes |
| Country ISO-2/ISO-3 field | Yes |
| Additional Address 1 | No |
| Additional Address 2 | No |
| Sublocality | No |
It also asks for an Address Tag, a free-form name used to build the DQE fields created for this check.
Email Check
In Select a field, pick the field to validate:
| Field | Description |
|---|---|
| Email field | Your object's existing Email-type fields, or pick Custom Email at the bottom of the list to choose any field, not just one already typed as Email. |
Phone Check
In Select a field, pick the phone field, then set:
| Field | Description |
|---|---|
| Phone field | Pre-filled from your selection; pick Custom Phone at the bottom of the list to choose any field, not just one already typed as Phone. |
| Country ISO-2/ISO-3 field | The field holding the record's country code, used to parse the number. |
| Default ISO-2/ISO-3 Country | A 2 or 3-character fallback country code used when that field is empty. |
| Output Phone Format | The format applied to the validated number. |
| Output Phone Separator | Space, Point or Dash. |
Name Check
In Select a field, pick the Name field group to validate. If your object has a standard compound Name field, selecting it auto-fills the Salutation Field, First Name Field and Last Name Field from its own sub-fields.
To map fields that aren't part of a single standard compound Name field, choose Custom Name at the bottom of the list instead. This unlocks each sub-field for manual selection:
| Field | Required? |
|---|---|
| Salutation | Yes |
| First Name | Yes |
| Last Name | Yes |
It also asks for a Name Tag, a free-form name used to build the DQE fields created for this check — each custom Name Tag must be unique across the objects covered by the same process.
Related articles
Related to