Introduction to the Max Length Check
The Max Length check asserts that no value in a text field is longer than a configured number of characters. Use it to protect fixed-width codes, respect a downstream column limit, or keep free-text fields from growing past what the schema allows.
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 length property, NULL handling, arrays, 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 length, pairing rules, 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 Max Length check on a text field.
-
Edit a Check
Step-by-step tutorial for changing the length, the target field, the filter, or the coverage.
-
Delete a Check
Step-by-step tutorial for archiving a check and deleting it permanently.
-
Troubleshooting
Common problems with whitespace, NULLs, arrays, and anomaly reporting, and how to resolve them.
-
API
Payload shape and field notes for creating Max Length check programmatically.
-
FAQ
Short answers to questions about length counting, NULLs, arrays, and anomaly reporting.