Skip to main content

Values in range

Validations to check that column values, or aggregations of column values, fall within a defined numeric range. All range validations are inclusive by default — use the exclude options to make boundaries strict.


Column values must be in range

Every row in the column must have a value between the specified minimum and maximum.

Use this when you want to enforce a valid range at the row level — for example, an age column that should always be between 0 and 120, or a discount_percent column that should never exceed 100.

Parameters

NameTypeRequiredDescription
ColumnColumnThe column to validate.
Minimum valueNumberThe minimum allowed value.
Exclude minimum valueBooleanIf enabled, values must be strictly greater than the minimum.
Maximum valueNumberThe maximum allowed value.
Exclude maximum valueBooleanIf enabled, values must be strictly less than the maximum.

Example

order_iddiscount_percent
110
225
3110
Example 1Example 2
Columndiscount_percentdiscount_percent
Minimum value00
Exclude minimum valuefalsefalse
Maximum value100150
Exclude maximum valuefalsefalse
Result❌ Fails✅ Passes
ReasonRow 3 has value 110, which exceeds the maximum of 100All values are within [0, 150]

Column values must be greater than

Every row in the column must have a value strictly greater than the specified minimum.

Use this when you want to ensure a column never contains zero or negative values — for example, a price or quantity column.

Parameters

NameTypeRequiredDescription
ColumnColumnThe column to validate.
Minimum valueNumberThe value that all column values must exceed.

Example

product_idprice
19.99
20
349.99
Example 1Example 2
Columnpriceprice
Minimum value0-1
Result❌ Fails✅ Passes
ReasonRow 2 has value 0, which is not strictly greater than 0All values are greater than -1

Column values must be greater or equal than

Every row in the column must have a value greater than or equal to the specified minimum.

Use this when you want to allow zero but disallow negative values — for example, a quantity column where 0 is valid but negative numbers are not.

Parameters

NameTypeRequiredDescription
ColumnColumnThe column to validate.
Minimum valueNumberThe minimum allowed value (inclusive).

Example

order_idquantity
13
20
3-1
Example 1Example 2
Columnquantityquantity
Minimum value0-5
Result❌ Fails✅ Passes
ReasonRow 3 has value -1, which is less than 0All values are greater than or equal to -5

Column values must be lower than

Every row in the column must have a value strictly less than the specified maximum.

Use this when you want to enforce a strict upper bound — for example, a score column that must always be less than 100 (not equal to it).

Parameters

NameTypeRequiredDescription
ColumnColumnThe column to validate.
Maximum valueNumberThe value that all column values must be below.

Example

student_idscore
185
2100
372
Example 1Example 2
Columnscorescore
Maximum value100101
Result❌ Fails✅ Passes
ReasonRow 2 has value 100, which is not strictly less than 100All values are less than 101

Column values must be lower or equal than

Every row in the column must have a value less than or equal to the specified maximum.

Use this when you want to enforce an inclusive upper bound — for example, a rating column that can go up to 5 but no higher.

Parameters

NameTypeRequiredDescription
ColumnColumnThe column to validate.
Maximum valueNumberThe maximum allowed value (inclusive).

Example

review_idrating
14
25
36
Example 1Example 2
Columnratingrating
Maximum value510
Result❌ Fails✅ Passes
ReasonRow 3 has value 6, which exceeds the maximum of 5All values are less than or equal to 10

Column minimum value must be in range

The minimum value found in the column must fall between the specified bounds.

Use this when you want to monitor the lower end of a numeric column without checking individual rows — for example, ensuring the cheapest product in a catalog never drops below a floor price.

Parameters

NameTypeRequiredDescription
ColumnColumnThe column to validate.
Minimum valueNumberThe lower bound for the column minimum.
Exclude minimum valueBooleanIf enabled, the column minimum must be strictly greater than this bound.
Maximum valueNumberThe upper bound for the column minimum.
Exclude maximum valueBooleanIf enabled, the column minimum must be strictly less than this bound.

Example

product_idprice
19.99
224.99
349.99

The minimum value in price is 9.99.

Example 1Example 2
Columnpriceprice
Minimum value105
Exclude minimum valuefalsefalse
Maximum value5050
Exclude maximum valuefalsefalse
Result❌ Fails✅ Passes
ReasonColumn minimum is 9.99, which is below the allowed bound of 10Column minimum 9.99 is within [5, 50]

Column maximum value must be in range

The maximum value found in the column must fall between the specified bounds.

Use this when you want to monitor the upper end of a numeric column without checking individual rows — for example, ensuring the largest transaction in a batch never exceeds an expected ceiling.

Parameters

NameTypeRequiredDescription
ColumnColumnThe column to validate.
Minimum valueNumberThe lower bound for the column maximum.
Exclude minimum valueBooleanIf enabled, the column maximum must be strictly greater than this bound.
Maximum valueNumberThe upper bound for the column maximum.
Exclude maximum valueBooleanIf enabled, the column maximum must be strictly less than this bound.

Example

transaction_idamount
1150
2980
312500

The maximum value in amount is 12500.

Example 1Example 2
Columnamountamount
Minimum value00
Exclude minimum valuefalsefalse
Maximum value1000015000
Exclude maximum valuefalsefalse
Result❌ Fails✅ Passes
ReasonColumn maximum is 12500, which exceeds the allowed bound of 10000Column maximum 12500 is within [0, 15000]

Column mean value must be in range

The mean (average) of all values in the column must fall between the specified bounds.

Use this when you want to monitor the central tendency of a numeric column over time — for example, ensuring the average order value stays within an expected range, which could indicate pricing or data issues if it drifts.

Parameters

NameTypeRequiredDescription
ColumnColumnThe column to validate.
Minimum valueNumberThe lower bound for the column mean.
Exclude minimum valueBooleanIf enabled, the column mean must be strictly greater than this bound.
Maximum valueNumberThe upper bound for the column mean.
Exclude maximum valueBooleanIf enabled, the column mean must be strictly less than this bound.

Example

order_idamount
150
280
3200

The mean of amount is 110.

Example 1Example 2
Columnamountamount
Minimum value00
Exclude minimum valuefalsefalse
Maximum value100200
Exclude maximum valuefalsefalse
Result❌ Fails✅ Passes
ReasonColumn mean is 110, which exceeds the allowed bound of 100Column mean 110 is within [0, 200]

Column median value must be in range

The median of all values in the column must fall between the specified bounds.

Use this when you want to monitor the typical value in a numeric column, robust to outliers — for example, ensuring the median delivery time stays within SLA expectations even when some deliveries are very late.

Parameters

NameTypeRequiredDescription
ColumnColumnThe column to validate.
Minimum valueNumberThe lower bound for the column median.
Exclude minimum valueBooleanIf enabled, the column median must be strictly greater than this bound.
Maximum valueNumberThe upper bound for the column median.
Exclude maximum valueBooleanIf enabled, the column median must be strictly less than this bound.

Example

shipment_iddelivery_days
12
23
34
430

The median of delivery_days is 3.5.

Example 1Example 2
Columndelivery_daysdelivery_days
Minimum value11
Exclude minimum valuefalsefalse
Maximum value35
Exclude maximum valuefalsefalse
Result❌ Fails✅ Passes
ReasonColumn median is 3.5, which exceeds the allowed bound of 3Column median 3.5 is within [1, 5]

Column sum must be in range

The sum of all values in the column must fall between the specified bounds.

Use this when you want to validate totals — for example, ensuring the total revenue in a daily batch falls within an expected range, or that the sum of allocated percentages in a distribution table adds up to a known value.

Parameters

NameTypeRequiredDescription
ColumnColumnThe column to validate.
Minimum valueNumberThe lower bound for the column sum.
Maximum valueNumberThe upper bound for the column sum.

Example

order_idamount
1150
2320
385

The sum of amount is 555.

Example 1Example 2
Columnamountamount
Minimum value600500
Maximum value10001000
Result❌ Fails✅ Passes
ReasonColumn sum is 555, which is below the allowed minimum of 600Column sum 555 is within [500, 1000]

Column proportion of unique values must be in range

The proportion of unique values in the column (unique count / total count) must fall between the specified bounds.

Use this when you want to monitor cardinality relative to total rows — for example, ensuring a customer_id column has high uniqueness, or that a category column doesn't have too many or too few distinct values relative to the dataset size.

Parameters

NameTypeRequiredDescription
ColumnColumnThe column to validate.
Minimum valueNumberThe minimum proportion of unique values. Must be between 0 and 1.
Exclude minimum valueBooleanIf enabled, the proportion must be strictly greater than the minimum.
Maximum valueNumberThe maximum proportion of unique values. Must be between 0 and 1.
Exclude maximum valueBooleanIf enabled, the proportion must be strictly less than the maximum.

Example

order_idcategory
1electronics
2clothing
3electronics
4food

category has 3 unique values out of 4 rows, so the proportion is 0.75.

Example 1Example 2
Columncategorycategory
Minimum value0.80.5
Exclude minimum valuefalsefalse
Maximum value11
Exclude maximum valuefalsefalse
Result❌ Fails✅ Passes
ReasonProportion is 0.75, which is below the allowed minimum of 0.8Proportion 0.75 is within [0.5, 1]

Column total unique values must be in range

The total number of distinct values in the column must fall between the specified bounds.

Use this when you want to monitor the absolute cardinality of a column — for example, ensuring a country column always has at least the expected number of countries, or that a lookup table hasn't grown beyond a known size.

Parameters

NameTypeRequiredDescription
ColumnColumnThe column to validate.
Minimum valueNumberThe minimum number of unique values allowed.
Maximum valueNumberThe maximum number of unique values allowed.

Example

sale_idcountry
1Argentina
2Brazil
3Argentina
4Chile

country has 3 distinct values.

Example 1Example 2
Columncountrycountry
Minimum value52
Maximum value1010
Result❌ Fails✅ Passes
ReasonTotal unique values is 3, which is below the allowed minimum of 5Total unique values 3 is within [2, 10]

Column values must be lower or equal than current date

Every row in the column must have a date value less than or equal to today's date. Fails if any row contains a future date.

Use this when you want to ensure a date column never contains future values — for example, a birth_date, created_at, or signed_at column that should always be in the past or today.

Parameters

NameTypeRequiredDescription
ColumnColumnThe column to validate. Must contain date or timestamp values.

Example

user_idbirth_datesigned_at
11990-05-122024-01-15
22001-11-302025-03-08
32031-04-012026-04-20
Example 1Example 2
Columnbirth_datesigned_at
Result❌ Fails✅ Passes
ReasonRow 3 has 2031-04-01, which is a future dateAll values in signed_at are on or before today's date