Introduction to the Min Value Check
The Min Value check asserts that every value in a numeric field is strictly greater than a configured floor. The floor itself is rejected: the comparison is value > minimum. Use it to keep an amount, a quantity, or a score above a known lower 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 floor 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 floor, 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 Min Value check with a lower limit.
-
Edit a Check
Step-by-step tutorial for moving the floor, 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 exclusive floor, NULLs, nested array fields, and anomaly reporting, and how to resolve them.
-
API
Payload shape and field notes for creating a Min Value check programmatically.
-
FAQ
Short answers to questions about the floor, exclusivity, NULLs, and anomaly reporting.