Introduction to the Between Check
The Between check asserts that every value in a numeric field falls inside a minimum and maximum boundary, with each side independently inclusive or exclusive. Use it to enforce a valid range such as an age, a percentage, a score, or a monetary amount.
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, properties, boundary inclusivity, NULL handling, 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 boundaries, setting inclusivity, 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 Between check with a minimum and a maximum boundary.
-
Edit a Check
Step-by-step tutorial for changing the boundaries, inclusivity, filter, coverage, or organizational properties.
-
Delete a Check
Step-by-step tutorial for archiving a check and deleting it permanently.
-
Troubleshooting
Common problems with boundary inclusivity, NULLs, type mismatches, and anomaly reporting, and how to resolve them.
-
API
Payload shape and field notes for creating a Between check programmatically.
-
FAQ
Short answers to questions about boundaries, inclusivity, NULLs, and anomaly reporting.