Create a Less Than Field Check¶
DQ Creating checks
Step-by-step tutorial for creating Less Than Field check that compares two fields on the same row. 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 Less Than Field 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 target field: the left side of the comparison. | |
| 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 | Uses the value of another field on the violating row as the anomaly message instead of the default one. Enabling it shows an Anomaly Message Field dropdown where you pick that field. When the selected field is empty for a violating row, the default message is used. |
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 |
|---|---|---|---|
| Field to compare | Option | The other field on the same row that the target field is compared against. | |
| Inclusive | Toggle | Whether two equal values pass. On, the comparison is <=; off, it is <. |
Comparators¶
| Field | Required | Type | Description |
|---|---|---|---|
| Numeric | Toggle | Enables an optional tolerance for numeric fields, so values within the configured margin still pass. Turning it on displays Comparison and Threshold. | |
| Comparison | Option | How the tolerance is measured. Absolute Value uses a fixed margin; Percentage Value uses a percentage of the compared field's value. | |
| Threshold | Number or Percentage | The allowed margin. The field is labeled Percentage Threshold when Percentage Value is selected. | |
| Datetime | Toggle | Enables an optional tolerance for date and timestamp fields. Turning it on displays Unit and Value. | |
| Unit | Option | The unit the tolerance is expressed in: Millis, Seconds, or Days. | |
| Value | Number | The allowed margin, in the selected Unit. |
Pass Criteria¶
| Field | Required | Type | Description |
|---|---|---|---|
| Coverage | Slider | The percentage of evaluated rows that must pass. Defaults to 100%; lower it only when a known fraction of rows is allowed to fail. |
Impact¶
| Field | Required | Type | Description |
|---|---|---|---|
| Metrics | List | Impact metrics that measure how big a failure is, such as the total amount or the number of customers in the failed records. With an expected range, a metric outside it raises the anomaly's impact and can tag the anomaly. Click Add your first impact metric to start. See Impact Metrics. |
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. |
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, "start date must be earlier than the end date") 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.
Step 3: Select Less Than Field in the Rule Type dropdown.
Step 4: Fill in the remaining Target fields: the table or file, the Field that forms the left side of the comparison, and, optionally, a Filter Clause and Custom Anomaly Description.
Step 5: Under Properties, pick the Field to compare: the other column on the same row. Decide with Inclusive whether two equal values pass. Optionally, set a comparator to tolerate small differences.
Step 6: Fill in the Pass Criteria, 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.