Create a Distinct Count Check¶
DQ Creating checks
Step-by-step tutorial for creating a Distinct Count check on a field's cardinality. For what each property means and how the rule evaluates the data, see the How It Works page.
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 page for the full matrix.
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.
Target¶
| Field | Required | Type | Description |
|---|---|---|---|
| Associate with a Check Template | 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 | Option | The validation logic to apply. Select Distinct Count for this check. Shown only while Associate with a Check Template is off. | |
| Table / File | Option | The table or file the check runs against. Locked after the check is saved. | |
| Field | Option | The field whose distinct values are counted. Every field type is accepted, and the check takes exactly one. | |
| Filter Clause | Text | A SQL WHERE expression that limits the rows the check evaluates. Rows outside the filter are ignored entirely. |
|
| Custom Anomaly Description | Toggle | Has no effect on this rule. The option replaces the message on Record Anomalies, and Distinct Count emits a Shape Anomaly only. |
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.
A filter that can never run
Validate refuses a filter clause that can never convert a value, such as amount <> '' on a number field, or that uses a function Qualytics does not allow, and names the reason. This applies to every rule type that accepts a filter, including checks that compute one value for the whole table, such as Sum, and checks with a coverage below 100%. If a check with such a filter reaches a scan, it is reported as Not Asserted with that reason, and the other checks on the table still run.
Properties¶
| Field | Required | Type | Description |
|---|---|---|---|
| Comparison | Text | The operator applied between the measured count and Value: Less Than, Less Than Or Equal To, Equal To, Greater Than Or Equal To, or Greater Than. | |
| Value | Text | The expected number of distinct values the comparison is made against. |
Ownership¶
| Field | Required | Type | Description |
|---|---|---|---|
| Owner | Option | The user responsible for the check. Already filled in with the check creator. | |
| Anomaly Assignee | Option | The user automatically assigned to anomalies the check produces. |
Metadata¶
| Field | Required | Type | Description |
|---|---|---|---|
| Description | 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 | Option | Tags applied to the check for filtering and organization. | |
| Additional Metadata | Key-value | Custom key-value pairs, typically links to catalog entries, tickets, or governance records. |
No Pass Criteria section
Distinct Count does not use coverage, so the form shows no Coverage slider.
Let AgentQ fill in the form
When AgentQ 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 status column should hold exactly seven distinct values") 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 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.
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 Distinct Count in the Rule Type dropdown.
Step 4: Fill in the remaining Target fields: the table or file, the Field whose values are counted, and, optionally, a Filter Clause.
Step 5: Under Properties, pick the Comparison operator and set the expected Value.
Step 6: Fill in the Ownership and 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.
Step 8: Click Save. A success message confirms that the check was created.