Date Range Component
Camila Escobar · June 17, 2026
The Date Range collects a start day and an end day as one answer, in one field.
Use it for rentals, bookings, leave requests, campaign windows, subscription terms — anything that runs from one day to another.
Settings
Setting | Effect |
Label | The question shown above the field |
Minimum date | Earliest day either end can be |
Maximum date | Latest day either end can be |
Required | The form will not submit while no range is picked |
Why not two date fields
You could build the same thing with two Date Pickers, and you would immediately inherit two problems this component solves for you.
The first is that the person can pick an end before the start. The range picker will not let them: choosing the second date always closes a valid interval.
The second is that the two halves can drift apart. As two separate columns, one can be edited, imported or cleared without the other, and you end up with rows that have a start and no end. As one range, they move together because they are one value.
The trap
A range is one value, not two columns. When you read it back — in a dashboard, an automation, or through the API — you get an object with a start and an end, not two separate fields.
That matters most in automations: a script that expects startDate and endDate as siblings on the row will find neither. Read the range field and take its two ends from inside it.
If you genuinely need the halves as independent columns — because you filter on the end date alone, or a formula computes from just the start — then two Date columns is the honest answer, and you accept the coordination cost.
Next
Praxsuite Forms: Components Overview
Date Picker Component
Datatypes in Praxsuite
How to Create a Form
Runs and Debugging