# Required Values Check Examples

Source: https://userguide.qualytics.io/data-quality-checks/required-values/deep-dive/examples/

Three real-world scenarios that show how the Required Values check is typically used in production: confirming a reference dimension survived a load, catching a category that stopped arriving, and validating a status enumeration. All three report a Shape Anomaly, because the rule evaluates the column as a set.

**Tab: Order Priorities Reference Set**

**The situation:** Orders carry one of five priority labels, and the operations dashboard has a lane for each. A load that drops a priority entirely leaves an empty lane, which reads as "no urgent orders today" rather than "the data is incomplete".

**Check configuration**

| Field | Value |
| --- | --- |
| Rule | Required Values |
| Field | `o_orderpriority` |
| Filter | *(none)* |
| Values | `1-URGENT`, `2-HIGH`, `3-MEDIUM`, `4-LOW`, `5-NOT URGENT` |
| Owner | *(check creator)* |
| Anomaly Assignee | *(Order Platform team)* |
| Description | Every order priority must be represented in the orders table. |
| Tags | `reference-data`, `completeness` |
| Additional Metadata | `jira: DATA-10600` |
| Status | Active |

**Payload**

```json
{
    "description": "Every order priority must be represented in the orders table.",
    "rule": "requiredValues",
    "fields": ["o_orderpriority"],
    "container_id": 145,
    "filter": null,
    "properties": {
        "list": ["1-URGENT", "2-HIGH", "3-MEDIUM", "4-LOW", "5-NOT URGENT"]
    },
    "tags": ["reference-data", "completeness"],
    "additional_metadata": {"jira": "DATA-10600"},
    "template_id": null,
    "status": "Active",
    "owner_id": 7,
    "default_anomaly_assignee_id": 12
}
```

**Sample Data**

| o_orderkey | o_orderpriority |
| --- | --- |
| 1 | 1-URGENT |
| 2 | 2-HIGH |
| 3 | 3-MEDIUM |
| 4 | 3-MEDIUM |

**What gets flagged**

The loaded rows hold three of the five required priorities. `4-LOW` and `5-NOT URGENT` never appear, so the check reports them as missing. No individual row is wrong, which is why the anomaly is raised against the column and carries no source records.

> **Example: Shape Anomaly**
>
> o_orderpriority is missing 2 of its required values: 4-LOW, 5-NOT URGENT

**Flowchart**

```mermaid
graph TD
    A["Collect the values in o_orderpriority"] --> B{"Does every required<br/>value appear at least once?"}
    B -->|Yes| C["Check passes"]
    B -->|No| D["Shape Anomaly naming<br/>the values that never appeared"]
```

**Equivalent SQL**

```sql
-- The required values that never appear in the column.
SELECT v.required_value
FROM (VALUES ('1-URGENT'), ('2-HIGH'), ('3-MEDIUM'), ('4-LOW'), ('5-NOT URGENT'))
     AS v(required_value)
WHERE v.required_value NOT IN (
    SELECT DISTINCT o_orderpriority FROM orders
);
```

**Tab: A Region That Stopped Arriving**

**The situation:** Sales land from four regions every day. When one region's feed breaks, the rows simply stop, and totals look plausible because the other three still report. Scoping the check to the current day turns a silent gap into an alert on the morning it happens.

**Check configuration**

| Field | Value |
| --- | --- |
| Rule | Required Values |
| Field | `region_code` |
| Filter | `sale_date = current_date()` |
| Values | `EMEA`, `NAMER`, `LATAM`, `APAC` |
| Owner | *(check creator)* |
| Anomaly Assignee | *(Sales Data team)* |
| Description | Every region must report sales each day. |
| Tags | `completeness`, `daily-feed` |
| Additional Metadata | `jira: DATA-10617` |
| Status | Active |

**Payload**

```json
{
    "description": "Every region must report sales each day.",
    "rule": "requiredValues",
    "fields": ["region_code"],
    "container_id": 512,
    "filter": "sale_date = current_date()",
    "properties": {
        "list": ["EMEA", "NAMER", "LATAM", "APAC"]
    },
    "tags": ["completeness", "daily-feed"],
    "additional_metadata": {"jira": "DATA-10617"},
    "template_id": null,
    "status": "Active",
    "owner_id": 7,
    "default_anomaly_assignee_id": 47
}
```

**Sample Data** (filtered to `sale_date = current_date()`)

| sale_id | region_code | sale_date |
| --- | --- | --- |
| S-01 | EMEA | 2026-03-11 |
| S-02 | NAMER | 2026-03-11 |
| S-03 | EMEA | 2026-03-11 |
| S-04 | LATAM | 2026-03-11 |

**Why the filter matters**

Here the filter is the point of the check. Without it, `APAC` would pass on the strength of yesterday's rows and the broken feed would go unnoticed. Scoping to the current day requires each region to report **today**.

**What gets flagged**

Three regions reported and `APAC` did not: its feed failed overnight. Because the filter narrows where a required value may appear, the absence is caught on the day it happens rather than whenever someone notices the totals look low. The message names the field and the missing region; it does not repeat the filter, so the description is where the daily scope has to be stated.

> **Example: Shape Anomaly**
>
> region_code is missing 1 of its required values: APAC

**Flowchart**

```mermaid
graph TD
    A["Apply filter: sale_date = current_date()"] --> B["Collect the values in region_code"]
    B --> C{"Does every region<br/>appear at least once today?"}
    C -->|Yes| D["Check passes"]
    C -->|No| E["Shape Anomaly naming<br/>the missing region"]
```

**Equivalent SQL**

```sql
-- The regions that did not report today.
SELECT v.region_code
FROM (VALUES ('EMEA'), ('NAMER'), ('LATAM'), ('APAC')) AS v(region_code)
WHERE v.region_code NOT IN (
    SELECT DISTINCT region_code
    FROM sales
    WHERE sale_date = current_date()
);
```

**Tab: Status Enumeration After a Migration**

**The situation:** A migration rewrote a ticket status column to a new vocabulary. Every status in the new set must be represented, otherwise part of the mapping was never applied and those tickets are sitting under an old label the application no longer understands.

**Check configuration**

| Field | Value |
| --- | --- |
| Rule | Required Values |
| Field | `status` |
| Filter | *(none)* |
| Values | `open`, `in_progress`, `blocked`, `resolved`, `closed` |
| Owner | *(check creator)* |
| Anomaly Assignee | *(Migration team)* |
| Description | Every status in the new vocabulary must be present after the migration. |
| Tags | `migration`, `completeness` |
| Additional Metadata | `jira: DATA-10634` |
| Status | Active |

**Payload**

```json
{
    "description": "Every status in the new vocabulary must be present after the migration.",
    "rule": "requiredValues",
    "fields": ["status"],
    "container_id": 733,
    "filter": null,
    "properties": {
        "list": ["open", "in_progress", "blocked", "resolved", "closed"]
    },
    "tags": ["migration", "completeness"],
    "additional_metadata": {"jira": "DATA-10634"},
    "template_id": null,
    "status": "Active",
    "owner_id": 7,
    "default_anomaly_assignee_id": 41
}
```

**Sample Data**

| ticket_id | status |
| --- | --- |
| T-01 | open |
| T-02 | in_progress |
| T-03 | resolved |
| T-04 | closed |

**What gets flagged**

Four of the five statuses appear. `blocked` never does, because the migration mapping had no rule for the old `on_hold` label and those tickets kept it. The rule reports the missing status; pairing it with an [Expected Values](https://userguide.qualytics.io/data-quality-checks/expected-values/introduction/) check would additionally report the leftover `on_hold` rows, which is the other half of the same problem.

> **Example: Shape Anomaly**
>
> status is missing 1 of its required values: blocked

**Flowchart**

```mermaid
graph TD
    A["Collect the values in status"] --> B{"Does every status in the<br/>new vocabulary appear?"}
    B -->|Yes| C["Check passes"]
    B -->|No| D["Shape Anomaly naming<br/>the missing status"]
```

**Equivalent SQL**

```sql
-- The statuses from the new vocabulary that never appear.
SELECT v.status
FROM (VALUES ('open'), ('in_progress'), ('blocked'), ('resolved'), ('closed'))
     AS v(status)
WHERE v.status NOT IN (SELECT DISTINCT status FROM tickets);
```

## See Also

- **Best Practices**

  Guidelines for choosing the list, scoping with a filter, and pairing the rule with Expected Values.

  [Best Practices](https://userguide.qualytics.io/data-quality-checks/required-values/deep-dive/best-practices/)
- **Permissions**

  The team permission each action needs: view, create, edit, archive, restore, and delete.

  [Permissions](https://userguide.qualytics.io/data-quality-checks/required-values/deep-dive/permissions/)
- **How It Works**

  The complete reference: definition, field scope, the value list, how it differs from Expected Values, the distinct-value limit, and why coverage does not apply.

  [How It Works](https://userguide.qualytics.io/data-quality-checks/required-values/deep-dive/how-it-works/)
- **Anomaly Reporting**

  The Shape Anomaly the check produces, what it reports, and why there are no source records to inspect.

  [Anomaly Reporting](https://userguide.qualytics.io/data-quality-checks/required-values/deep-dive/anomaly-reporting/)

*Last updated: September 22, 2026.*
