# Create a Field Count Check

Source: https://userguide.qualytics.io/data-quality-checks/field-count/how-tos/create-a-check/

*Requires the Data Observability (DO) module.*

Step-by-step tutorial for creating a Field Count check on a container. For what each property means and how the rule evaluates the data, see the [How It Works](https://userguide.qualytics.io/data-quality-checks/field-count/deep-dive/how-it-works/) page.

> **Note: Permission Required**
>
> You need the **Author** team permission on the datastore to create an Active check, or **Drafter** to create it as a Draft. See the [Permissions](https://userguide.qualytics.io/data-quality-checks/field-count/deep-dive/permissions/) page for the full matrix.

> **Tip: Show me how**
>
> The app can walk you through this. Click **Show me how**  in the check creation form's header, or press `H` while it is open, and the **Add a Check** walkthrough highlights each step while you fill in the real form.

## Field reference

The **Authored Check Details** form is organized in the sections below. Fill them in as you follow the [Steps](https://userguide.qualytics.io/data-quality-checks/field-count/how-tos/create-a-check/#steps).

### Target

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Associate with a Check Template** | No | Toggle | Links the check to a Check Template. Enabling it replaces the **Rule Type** dropdown with a **Template** dropdown where you pick an existing template, which then controls the check's properties. When off, you configure everything on this form. |
| **Rule Type** | Yes | Option | The validation logic to apply. Select **Field Count** for this check. Shown only while **Associate with a Check Template** is off. |
| **Table / File** | Yes | Option | The table or file whose field count is asserted. Locked after the check is saved. |

> **Tip: Create the table or file from the form**
>
> If the table or file you need does not exist yet, click **Add Computed Table**  next to the **Table / File** field while it is empty (**Add Computed File** on a file-based datastore). Once saved, the new one is selected and pinned to the top of the list with a  icon until you close the form. The button appears only with the **Author** or **Editor** team permission on the datastore, and not when you add a check from Explore.

### Properties

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Number of Fields** | Yes | Number | The exact number of fields the container must hold. |

### Ownership

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Owner** | Yes | Option | The user responsible for the check. Already filled in with the check creator. |
| **Anomaly Assignee** | No | Option | The user automatically assigned to anomalies the check produces. |

### Metadata

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Description** | Yes | Text | A plain-language description of what the check enforces. Supports Markdown formatting: click the field to open the Markdown editor. Click the **Apply suggested description**  button for a suggestion based on the rule type. |
| **Tags** | No | Option | Tags applied to the check for filtering and organization. |
| **Additional Metadata** | No | Key-value | Custom key-value pairs, typically links to catalog entries, tickets, or governance records. |

> **Info: Fields the form does not show**
>
> Field Count selects no columns and evaluates no rows, so the form offers no **Field** picker, no **Filter Clause**, no **Coverage** slider, and no **Custom Anomaly Description** toggle.

> **Tip: Let AgentQ fill in the form**
>
> When [AgentQ](https://userguide.qualytics.io/agentq/getting-started/) is configured for your deployment, the **Check Assistant** panel in the check form can author the check for you: describe the rule in plain language (for example, "the orders extract must always have nine columns") and it proposes a configuration you can apply to the form. Review the filled-in fields, then Validate and Save as usual.

## Steps

Each field is described in the [Field reference](https://userguide.qualytics.io/data-quality-checks/field-count/how-tos/create-a-check/#field-reference) above.

**Step 1**: Select the source datastore from the left menu, then click the **Checks** tab.

**Step 2**: Click **Add** in the top-right corner and select **Check** from the dropdown. The **Authored Check Details** form opens.

> **Warning: No tables available**
>
> On a datastore that has no tables yet, for example one that was just added and has not been synced, the form shows a **No tables available** warning (**No files available** on a file-based datastore) that reads **Run a Sync on this datastore before adding checks.** instead of the check fields. When you open the form from the datastore page and you can run operations on the datastore, the warning also offers a **Run Sync**  button, which closes the form and opens the Sync dialog. Add the check once the Sync finishes. The warning does not appear when you add a check from a check template.

**Step 3**: Select **Field Count** in the **Rule Type** dropdown.

**Step 4**: Select the table or file whose shape you want to assert. Field Count has no **Field** picker, no **Filter Clause**, and no **Coverage**: the rule evaluates the container itself.

**Step 5**: Under [Properties](https://userguide.qualytics.io/data-quality-checks/field-count/how-tos/create-a-check/#properties), set **Number of Fields** to the exact count the container must hold.

**Step 6**: Fill in the [Ownership](https://userguide.qualytics.io/data-quality-checks/field-count/how-tos/create-a-check/#ownership) and [Metadata](https://userguide.qualytics.io/data-quality-checks/field-count/how-tos/create-a-check/#metadata) sections. Only the **Description** is required.

**Step 7**: Click **Validate** to test the rule against the selected data without saving it. A success message confirms the rule can run on that data. If validation fails, see [Troubleshooting](https://userguide.qualytics.io/data-quality-checks/field-count/troubleshooting/#validation-fails-when-creating-the-check).

**Step 8**: Click **Save**. A success message confirms that the check was created.

*Last updated: November 10, 2026.*
