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

Start Date field: never after the due date

The date the work starts. It can’t fall after the due date in the same record.

2 min

How it works

Every start date in the unit is compared with every due date in the same record.

The same day is allowed.

When you edit, the new values are compared with the saved ones, so you can’t push the start past the existing due date.

The order isn’t checked if either date is empty, or if the field is hidden by conditional visibility.

An old record that breaks the rule can still have its other fields edited.

Regular date fields aren’t tied to this rule.

The update field action in automations doesn’t check the order.

If something goes wrong

What you see
Why
What to do
“Start date: must be on or before the due date”
The start is after the due date.
Correct one of the two dates.
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.