Introduction to the Max Value Check
The Max Value check asserts that no value in a numeric field exceeds a configured ceiling. The ceiling itself is accepted: the comparison is value <= maximum. Use it to cap an amount, a percentage, a quantity, or any measure with a known upper limit.
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 ceiling property, NULL handling, nested array fields, 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 ceiling, 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 a Max Value check with an upper limit.
-
Edit a Check
Step-by-step tutorial for moving the ceiling, or changing the filter, coverage, or organizational properties.
-
Delete a Check
Step-by-step tutorial for archiving a check and deleting it permanently.
-
Troubleshooting
Common problems with the inclusive ceiling, NULLs, nested array fields, and anomaly reporting, and how to resolve them.
-
API
Payload shape and field notes for creating a Max Value check programmatically.
-
FAQ
Short answers to questions about the ceiling, inclusivity, NULLs, and anomaly reporting.