Equal To Field Best Practices

Guidelines for getting reliable signal from Equal To Field checks while keeping the noise (and the maintenance) low.

Point the check at the column you trust

The rule proves the two columns agree, not that either is right. Decide which one is the source of truth, evaluate the copy against it, and say so in the description so whoever triages knows which side to fix.

Match the comparator to the field type

Set String for text that differs only in spacing, Datetime for timestamps written seconds apart, and Numeric for amounts that went through arithmetic. A comparator set for a type it does not cover is rejected with a 422 when the check is saved, so the mismatch surfaces at creation rather than in a quiet scan result.

Prefer this rule over a constant when the value moves

If the expected value changes with the business, Equal To goes stale the moment it does. Comparing against a column keeps the rule correct without maintenance.

Use Data Diff when the reference is another table

Equal To Field compares two columns of the same row. When the comparison spans two containers, Data Diff is the rule that pairs rows across them and reports what changed.

Keep coverage at 100% unless a known backlog exists

At 100% coverage every failing row is reported as a Record Anomaly, which tells you exactly which rows break the rule. Below 100% the check reports a single Shape Anomaly only when the failing fraction crosses the tolerance, and no per-row detail is produced. Lower coverage only while a known set of legacy rows is being cleaned up.

Scope with a filter instead of loosening coverage

When the rule only applies to part of the table (one segment, one channel, one period), express that with a filter clause rather than by lowering coverage. The filter removes the out-of-scope rows from evaluation entirely, and the expression is echoed in every anomaly message.

Route the anomalies to the right people

A failure usually points at the system that produced the value, not at the warehouse. Set an Anomaly Assignee from the team that owns that producer, and tag the check so related checks are easy to find.

See Also