Introduction to the Not Exists In Check
The Not Exists In check asserts that no value in a field appears in a field on another container. Use it for exclusion rules: a suppression list, a blocklist, or two sets that must stay disjoint.
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 reference lookup, NULL handling, both filter clauses, 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, scoping both sides, 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 a Not Exists In check against a reference field.
-
Edit a Check
Step-by-step tutorial for changing the reference container or field, or adjusting the filters and coverage.
-
Delete a Check
Step-by-step tutorial for archiving a check and deleting it permanently.
-
Troubleshooting
Common problems with the reference lookup, NULLs, type mismatches, and anomaly reporting.
-
API
Payload shape and field notes for creating a Not Exists In check programmatically.
-
FAQ
Short answers to questions about the reference, NULLs, filters, and anomaly reporting.