Satisfies Expression Anomaly Reporting
How the Satisfies Expression check reports violations: the anomaly messages it produces, what the numbers mean, how the offending record appears in Source Records, and how to replace the default message with a value from your own data.
Anomaly Messages
At 100% coverage, Satisfies Expression reports violating rows as Record Anomalies. Below 100% coverage, a failed coverage assertion produces one Shape Anomaly for the dataset. The two templates are:
Record Anomaly
Shape Anomaly
When a filter is set, both Record and Shape Anomaly messages end with [filter: <expression>].
Scan settings can group a large number of Record Anomalies into one rolled-up Shape Anomaly. This behavior applies across rule types and is documented under Maximum Record Anomalies per Check.
What the Numbers Mean
- X.XXX%: the fraction of filtered rows where the expression did not evaluate to true.
- N: the total number of rows the check evaluated (after the filter, if any).
- K: the number of rows that failed, including any where the expression returned nothing.
Source Records Behavior
Every column the expression references is highlighted with an orange outline and an orange-tinted background in the Source Records view, mirroring the platform's standard violation rendering. The check's field list is derived from the expression, so the highlight covers all the columns that took part in the comparison rather than a single offending value: read the expression in the message against those values to see which part did not hold.
Custom Anomaly Description
Satisfies Expression supports Custom Anomaly Description because it emits Record Anomalies. When anomaly_message_field (or the Custom Anomaly Description toggle in the UI) is set to another column on the same row, the Record Anomaly message becomes the value of that column for the violating row. When the referenced column is null, missing, or empty, the standard template is used instead.
Because the option only applies to Record Anomalies, it does not affect Shape Anomalies, which always use the fixed template.
See Also
-
Examples
Three production scenarios with sample data, anomaly messages, and the SQL equivalent of what the check evaluates.
-
Best Practices
Guidelines for writing expressions that stay readable, handling NULLs deliberately, and knowing when a dedicated rule is better.
-
Permissions
The team permission each action needs: view, create, edit, archive, restore, and delete.
-
How It Works
The complete reference: definition, field scope, what the expression must return, check variables, NULL handling, filter behavior, and coverage.