Introduction to the Unique Check
The Unique check asserts that no value repeats in a field, or that no combination of values repeats across a set of fields. Use it to enforce primary-key semantics, catch double-loaded rows, and guard composite keys on junction and line-item tables.
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, single-field and composite semantics, NULL handling, filter behavior, and coverage.
-
Anomaly Reporting
The anomaly message the check produces, what the counts mean, and how duplicate groups appear in Source Records.
-
Examples
Production scenarios with sample data, duplicate groups, and the resulting anomaly messages.
-
Best Practices
Guidelines for NULL handling, composite keys, scoping, and pairing rules.
-
Permissions
The team permission each action needs: view, create, edit, archive, restore, and delete.
-
Create a Check
Step-by-step tutorial for creating a Unique check on a single field or a composite key.
-
Edit a Check
Step-by-step tutorial for changing the key, filter, coverage, or organizational properties.
-
Delete a Check
Step-by-step tutorial for archiving a check and deleting it permanently.
-
Troubleshooting
Common problems with NULLs, composite keys, counts, and anomaly reporting, and how to resolve them.
-
API
Payload shape and field notes for creating a Unique check programmatically.
-
FAQ
Short answers to questions about NULLs, composite keys, coverage, and anomaly reporting.