All topics
Get started8Account, team & permissions44Units & fields70Records, views & tasks39WhatsApp & Cortex Chat68Email & social27Lead ads & distribution38Automations52Documents & quotes32Dashboards40Cortex AI18Developers & API12
Help Center·448 guidesAll topicsContact support

Make a field required, always or on a condition

A required field stops a record being saved empty. A conditionally required field becomes mandatory only when a condition on another field is met, such as “Cancellation reason” when the status is “Cancelled”.

4 min
Before you start · for owners
The permission to edit units
  • You need: The permission to edit units

Steps

1
Open the field’s settings.
2
Turn on Required field to make it always mandatory.
3
Or turn on Conditional requirement: choose the Trigger field, the Operator and the Trigger values.
4
Save.

Condition operators

Operator
Met when
equals
The trigger field’s value equals one of the values
does not equal
It equals none of them
is one of
One of the chosen values is present
is not one of
None of them is present
is empty
The trigger field has no value
is not empty
The trigger field has a value

Fields that can be a trigger: select, multi-select, status, priority, tag, text, number, true/false, date, email and phone, from the same unit.

The error message names the condition in the option’s words, such as “Reason is required when Status equals Cancelled”.

Required and hidden

A field hidden by a conditional visibility rule is never required, even if you turned on Required field. That way no one gets stuck on a field they can’t see.

A minimum length on long text doesn’t make the field required. An empty value is accepted unless the field is required.

If something goes wrong

What you see
Why
What to do
“{Field} is required” when saving
The field is required and empty.
Fill it in, or remove the requirement.
Saving the condition rule was refused
The trigger doesn’t exist or isn’t valid, or the field depends on itself.
Choose an active trigger of an allowed type.

A real example

Basma Clinics
The situation

Front desk staff cancel appointments without giving a reason.

What they did
  1. They made “Cancellation reason” required when the status equals “Cancelled”.
  2. They hid it for the other statuses with conditional visibility.
The result

Every cancellation has a clear reason in the reports.

A made-up company, to show the idea. The numbers are rounded.

Good to know

Relation, calculation and serial number fields can’t be required on a condition.
The trigger must be an active field in the same unit.
Required fields are checked when saving from the interface, imports, automations and AI.
Did this guide solve it?
If not, we’ll ask what was missing.
Open in Corteksa
Did this guide solve it?

We read every answer. To get a reply, use Contact support.