Introduction to the Expected Values Check
The Expected Values check asserts that every value in a field comes from a list of allowed values. Use it to enforce a controlled vocabulary such as status codes, currencies, or country codes, and to catch values that drift outside the agreed set.
This section is the complete guide to the check. The Deep Dive covers the definition, properties, and full evaluation semantics, explains how anomalies are reported, walks through production examples, and collects best practices; the How-tos are step-by-step tutorials for creating, editing, and deleting a check; the API page documents the payload for programmatic use; and the FAQ answers the most frequent questions.
Next Steps
-
How It Works
The complete reference: definition, field scope, properties, matching rules, arrays, filter behavior, and coverage.
-
Anomaly Reporting
The anomaly messages the check produces, what the numbers mean, Source Records highlighting, and Custom Anomaly Description.
-
Examples
Three production scenarios with sample data, anomaly messages, and the SQL equivalent of what the check evaluates.
-
Best Practices
Guidelines for sizing the vocabulary, matching exactly, pairing rules, and keeping the signal clean.
-
Permissions
The team permission each action needs: view, create, edit, archive, restore, and delete.
-
Create a Check
Step-by-step tutorial for creating an Expected Values check with a list of allowed values.
-
Edit a Check
Step-by-step tutorial for changing the allowed values, filter, coverage, or organizational properties.
-
Delete a Check
Step-by-step tutorial for archiving a check and deleting it permanently.
-
Troubleshooting
Common problems with type mismatches, exact matching, arrays, and anomaly reporting, and how to resolve them.
-
API
Payload shape and field notes for creating an Expected Values check programmatically.
-
FAQ
Short answers to questions about NULLs, matching, list size, and anomaly reporting.