Introduction to the Equal To Field Check
The Equal To Field check asserts that two columns on the same row hold the same value. Unlike a constant, the reference moves with the data, so the rule keeps meaning the right thing as the values change. Use it to keep a denormalized copy in step with its source, or to confirm two systems wrote the same figure.
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 compared field, the three comparators, 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 choosing the reference field, setting tolerances, and deciding between this rule 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 Field check between two columns.
-
Edit a Check
Step-by-step tutorial for changing the compared field or adjusting the comparators.
-
Delete a Check
Step-by-step tutorial for archiving a check and deleting it permanently.
-
Troubleshooting
Common problems with NULLs, type mismatches, formatting noise, and anomaly reporting.
-
API
Payload shape and field notes for creating an Equal To Field check programmatically.
-
FAQ
Short answers to questions about the compared field, comparators, NULLs, and anomaly reporting.