---
title: "Create a data quality policy"
slug: "bc-create-a-data-quality-policy"
description: "Create a Data Quality Policy in Dynamics 365 to manage master data tables, configure validation rules, and ensure data integrity effectively."
updated: 2026-08-05T06:06:09Z
published: 2026-08-05T06:06:09Z
canonical: "docs.staedean.com/bc-create-a-data-quality-policy"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a data quality policy

A Data Quality Policy is the top-level container that tells Data Quality Studio which master data table to govern. You create one policy per table. Every field validation rule and every duplicate check rule lives inside a version of a policy. Nothing gets evaluated at runtime until a policy exists, has at least one rule configured on a version, and that version has been set to **Active**.

**Purpose**

Create the policy record for a specific master data table so that validation rules and duplicate checks can be configured on it in subsequent steps.

**Navigation**

Use the **Tell Me** search (**Alt+Q**) and type **Data Policies**. Select **Data Policies** from the results.

The **Data Policies** list opens. This is where all policies in the system are managed.

### **Understanding the Data Policies List**

The **Data Policies** list shows every policy that has been set up, one row per governed table.

| **Column** | **Description** |
| --- | --- |
| **Policy Table ID** | The D365 BC table number of the entity being governed. Click this number to open the **Data Policy** form for that policy. Supported values in: **18** (Customer), **23** (Vendor), **5050** (Contact). |
| **Policy Table Caption** | The display name of the table. Populates automatically, when a **Policy Table ID** is selected. |
| **Version No.** | The version currently visible in this row. Typically the latest version. |
| **Active** | Indicates whether the version is active and enforcing rules |

**Policy Details factbox (right panel):**

When you select a row, the factbox on the right shows a summary of that policy's current state:

| **Field** | **Description** |
| --- | --- |
| **No. of Versions** | Total number of versions created for the policy, including Draft, Active, and Inactive |
| **Validation Fields** | Number of fields with at least one validation rule in the active version |
| **Validation Rules** | Total number of validation rules in the active version. |
| **Conditions** | Total conditions across all validation rules in the active version |
| **Filter Values** | Total filter values defined across all conditions |
| **Duplicate Rules** | Number of duplicate check rules in the active version. |

Use the factbox to get a quick health check on a policy without opening it. For example, to confirm that rules have not accidentally been deleted, or to see how many conditions are active.

### **Steps**

1. Press **Alt+Q** to open the **Tell Me** search.
2. Enter **Data Policies**.
3. Select **Data Policies** from the results. The list shows all existing policies. If none exist yet, the list is empty.
4. In the action bar, click **+ New**.
5. A new blank row is added with the cursor in the **Policy Table ID** field.

**Subtask: Select the master data table**

1. Click the lookup in the **Policy Table ID**.
2. Search for and select the required table:

| **Entity** | **Table ID** |
| --- | --- |
| Customer | 18 |
| Vendor | 23 |
| Contact | 5050 |

1. **Policy Table Caption** populates automatically with the table's display name.

> [!NOTE]
> **Note** Phase 1 officially supports Customer (18), Vendor (23), and Contact (5050). Other tables may be selectable but are not tested or supported in this phase.

> [!NOTE]
> **Note** Only **one policy is allowed per table**. If you attempt to create a second policy for a table that already has one, Microsoft Dynamics 365 Business Central will prevent it. If you need different rules for the same table, use versions instead of multiple policies.

1. D365 BC saves the row automatically when you move away from it. At this point, the system also creates **Version 1** of the policy in **Draft** state automatically. You will see **Version No. = 1** and **Active = off** in the row.
2. Click the **Policy Table ID** (the underlined number, e.g. **18**) value to open the **Data Policy** form for this policy. Use this page to manage versions, add validation rules, and configure duplicate checks.

### **Examples**

#### **Example 1 - Create a Customer Policy**

A company wants to enforce data quality rules on Customers.

1. Press **Alt+Q**, then enter **Data Policies**, and open the list.
2. Click **+ New** in the action bar.
3. In the **Policy Table ID** column, click the lookup and search for **Customer** or enter **18**.
4. Select **Customer (18)**. The **Policy Table Caption** auto-fills as **Customer**.
5. Move away from the row. D365 BC saves automatically and creates Version 1 (Draft).
6. The list now shows:

| **Policy Table ID** | **Policy Table Caption** | **Version No.** | **Active** |
| --- | --- | --- | --- |
| 18 | Customer | 1 | *(unchecked)* |

1. Click **18** to open the Data Policy form and continue with rule configuration.

**Policy Details factbox** at this stage:

| **Field** | **Value** |
| --- | --- |
| No. of Versions | 1 |
| Validation Fields | 0 |
| Validation Rules | 0 |
| Duplicate Rules | 0 |

#### **Example 2 - Full rollout: Customer, Vendor, and Contact**

A company wants Data Quality Studio active across all three supported entities.

Repeat the creation steps three times:

| **Policy Table ID** | **Policy Table Caption** |
| --- | --- |
| 18 | Customer |
| 23 | Vendor |
| 5050 | Contact |

Each policy is completely independent. Rules in one policy do not affect other policies. They can be at different version numbers and activated at different times.

After all three are created, the Data Policies list looks like this (before Anywhere Mobility Solutions rules are configured or versions activated):

| **Policy Table ID** | **Policy Table Caption** | **Version No.** | **Active** |
| --- | --- | --- | --- |
| 18 | Customer | 1 | *(off)* |
| 23 | Vendor | 1 | *(off)* |
| 5050 | Contact | 1 | *(off)* |

---

> [!NOTE]
> **Note** Creating a policy does **not** make it active. Rules run only after you configure them and activate a version. See [Create and Manage Policy Versions](https://portal.document360.io/manufacturing/docs/create-and-manage-policy-versions) for how to activate a version.