Introduction to the Not Empty Check
The Not Empty check asserts that a text field actually contains something. A column can be fully populated and still be useless if every value is an empty string or a run of spaces, and this is the rule that tells the two apart.
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, what counts as empty, how array fields behave, NULL handling, filter behavior, and coverage.
-
Anomaly Reporting
The anomalies the check produces on text and on array fields, and how the offending value appears in Source Records.
-
Examples
Three production scenarios with sample data, anomaly messages, and the SQL equivalent of what the check evaluates.
-
Best Practices
Guidelines for pairing it with Not Null, choosing between text and array behavior, and fixing blankness at the source.
-
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 Empty check on a text or array field.
-
Edit a Check
Step-by-step tutorial for changing the field, the filter, or the coverage on an existing check.
-
Delete a Check
Step-by-step tutorial for archiving a check and deleting it permanently.
-
Troubleshooting
Common problems with NULLs, whitespace, array fields, and anomaly reporting.
-
API
Payload shape and field notes for creating a Not Empty check programmatically.
-
FAQ
Short answers to questions about blank values, NULLs, array behavior, and anomaly reporting.