---
title: "Form rules with field value conditions"
slug: "form-rules-with-field-value-conditions"
updated: 2026-04-29T17:03:03Z
published: 2026-04-29T17:03:03Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.quickbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Form rules with field value conditions

You can create rules with conditions that trigger actions the value in a field matches the criteria you select. When you build a rule with a field value condition, you can select the field, the operator by which the rule will evaluate the value, and the value.

For example, if you wanted to create a rule for your client management form that requires users to schedule a new appointment with a client when more than 30 days have passed since their last contact, you would need to create a rule with a field value condition that triggers an action that makes the fields in the appointment section required when the value in the days since last contact field is greater than 30 days.

![The form rule builder showing a field value condition with the days since last contact field set to is greater than 30](https://cdn.document360.io/dd260e4e-10bb-4b66-8fb3-5504c272b904/Images/Documentation/15963817419668.png)

## Field value condition operators

Each field value condition contains an operator that tells the form rule how to evaluate the field value.

| Operator | Description |
| --- | --- |
| Is equal to | The value in the field must be equal to selected value exactly **Note:**When used with list - user and multi-select text fields, only all of the selected values can appear in the field to be true. |
| Is not equal to | The value in the field must not be equal to the selected value **Note:**When used with list - user and multi-select text fields, the values that appear in the field can not equal to the exact set of values specified in the selected values to be true. |
| includes | The value in the field can match the selected value exactly, or it can contain the exact selected value along with other values |
| Does not include | The value in the field cannot contain the selected value |
| is less than | The value must be less than the selected value |
| is lower than alphabetically | Quickbase uses alphabetical order to determine whether a value is lower than the selected value |
| is greater than | The value must be greater than the selected value |
| is higher than alphabetically | Quickbase uses alphabetical order to determine whether a value is higher than the selected value |
| is less than or equal to | The value must be less than or equal to the selected value to be true |
| is lower than or equal to alphabetically | Quickbase uses alphabetical order to determine whether a value is lower than or equal to the selected value |
| is greater than or equal to | The value must be greater than or equal to the selected value to be true. For text fields |
| is higher than or equal to alphabetically | Quickbase uses alphabetical order to determine whether a value is higher than or equal to the selected value |
| is before | The date/time in the field must occur chronologically before the selected value |
| is after | The date/time in the field must occur chronologically after the selected value |
| is on or before | The date/time in the field must occur on or chronologically before the selected value |
| is on or after | The date/time in the field must occur on or after the selected value |
| is during | The date/time in the field must occur within the selected value range |
| is not during | The date in the field must not occur within the selected value range |
| starts with | The value in the field must start with the selected value |
| does not start with | The value in the field must not start with the selected value |
| is the current user | The user must match the selected user |
| filename contains | The name of the file that appears in the field can match the selected values exactly, or it can contain those values and other values as well |
| filename does not contain | The name of the file that appears in the field can not match the selected values exactly, and it can not contain those values |
| filename is equal to | The name of the file that appears in the field must match the selected value exactly |
| filename is not equal to | The name of the file that appears in the field must must not match the selected value exactly |
| filename starts with | The name of the file that appears in the field must start with the selected value |
| filename does not start with | The name of the file that appears in the field must not start with the selected value |
| contains | The value in the field must contain the exact selected value |
| does not contain | The value in the field must not contain the exact selected value. |

## Build field value condition rules with the is equal to operator

Example: If you wanted to capture sales details on a sales volume tracking form when users indicate they have completed a sale, you could use the is equal to operator to create a rule to display and require a multi-select field for users to select the products they sold to each client.

To build your rule you would select:

**When**

sale (*checkbox field)*

is equal to

checked

**Then**

show

field

products sold

*Add action*

require

field

products sold

## Build field value condition rules with the is less than operator

Example: If you wanted to display a message to users to reorder items with low inventory, you can use the is less than operator.

To build your rule, you would select

**When**

the user

is in this role

Manager

and

units in stock

is less than

the value

50

**Then**

display message

modal

"Complete reorder form for this item within 72 hours."
