Feature Request: “Is Set / Is Not Set” Conditions for Date/Time Fields (Visibility + Actions)

Roadmap Feature Requests
, ,
1

Hey Adalo team & community :waving_hand:

Here’s an issue that’s been plaguing me for a while:

When using visibility conditions or action conditions on a Date/Time field, we only have:

  • Is before
  • Is after
  • Is between

But there’s no option for:

  • Is set
  • Is not set

The Problem

If a Date/Time field is unset (empty/null), there is currently no way to check for that state.

That means we cannot:

  • Show a button only if a date has not been set
  • Show a label only if a date has been set
  • Trigger an action only if a Date field exists
  • Hide components when the Date is empty

There is also no true workaround for this. You cannot reliably detect a null Date/Time field using the current condition options.

Why This Matters

In real-world apps, Date/Time fields are often:

  • Optional
  • Assigned later in a workflow
  • Used to determine status (draft vs scheduled, published vs unpublished, active vs expired, etc.)

Without “Is set” or “Is not set,” we cannot properly manage these common states in UI logic or action flows.

Suggested Improvement

Add two additional condition options for Date/Time fields:

  • Is set
  • Is not set

Ideally available in:

  • Component visibility settings
  • Action conditional logic

This would bring Date/Time logic in line with how null states are expected to work in modern no-code platforms.

This feels like a small addition, but it would unlock a ton of flexibility in real-world apps.

3 Likes