Introduction to the Equal To Check
The Equal To check asserts that one or more numeric fields hold a specific constant on every row. Select several fields and they are asserted together: each one must equal the value. Use it to pin a column that should never vary, or to catch a field that drifted away from its expected constant.
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, the expected value, inclusivity, the numeric tolerance, NULL handling, 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 pinning constants, using tolerance, and choosing between Equal To and its alternatives.
-
Permissions
The team permission each action needs: view, create, edit, archive, restore, and delete.
-
Create a Check
Step-by-step tutorial for creating an Equal To check on one or more numeric fields.
-
Edit a Check
Step-by-step tutorial for changing the expected value, the tolerance, or the selected fields.
-
Delete a Check
Step-by-step tutorial for archiving a check and deleting it permanently.
-
Troubleshooting
Common problems with floating-point equality, NULLs, multi-field checks, and anomaly reporting.
-
API
Payload shape and field notes for creating an Equal To check programmatically.
-
FAQ
Short answers to questions about the expected value, tolerance, NULLs, and anomaly reporting.