Required Values Anomaly Reporting
How the Required Values check reports violations: the Shape Anomaly it produces, what it tells you, and why the anomaly carries no source records.
Anomaly Messages
Required Values emits a Shape Anomaly only, one per failed evaluation. The anomaly reports that the field does not hold every value the check requires, so what you act on is the list of values that never appeared.
The message follows a single template, with the missing values listed comma-separated:
For example, O_ORDERPRIORITY is missing 3 of its required values: 2-HIGH, 3-MEDIUM, 5-LOW. Above 25 values the list ends with and N others, or and 1 other for a single one.
There is no Record Anomaly variant. The violation belongs to the column as a whole: no individual row is at fault, because the problem is the absence of a row rather than the content of one.
For the same reason the Source Records view has nothing to list. A missing value has no record to point at, which is the main practical difference from Expected Values, where every violation is a row you can open.
The filter expression does not appear in the message. Name the scope in the check description instead.
Custom Anomaly Description does not apply to this rule. The option replaces the message on Record Anomalies, and Required Values emits a Shape Anomaly only.
See Also
-
Examples
Three production scenarios with sample data, the resulting anomaly, and the SQL equivalent of what the check evaluates.
-
Best Practices
Guidelines for choosing the list, scoping with a filter, and pairing the rule with Expected Values.
-
Permissions
The team permission each action needs: view, create, edit, archive, restore, and delete.
-
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.