The Date field is used to capture date and time information in a form. You use it when recording events, schedules, durations, or time-based records such as joining dates, appointments, or activity periods.
It supports multiple categories so you can collect only what is required, a date, a time, both, a range, or a duration.
Each category is designed for a specific type of Date & Time based input.
| Type | Description |
|---|---|
| Date |
Example
|
| Time |
Example
|
| Date and Time |
Example
|
| Date Range |
Example
|
| Duration |
Use it when the length of time matters more than exact start and end points. Example
|
Note
This field includes all standard field properties. For details, refer to Form Field Properties. The additional properties specific to this field are listed below.
1. Tag Calendar: This property links the Date field to a calendar source to control which dates are available or highlighted.
You can choose from three options:
| Options | Description |
|---|---|
| None |
|
| Predefined Calendar |
This allows the field to recognize:
|
| Calendar of Logged-in User |
|
| Type | Mistake | Impact | Fix |
|---|---|---|---|
| Using Date instead of Date and Time | You use the Date category when time information is required. |
|
Use the Date and Time category when both date and time matter. |
| Using Date Range for single-day inputs | You use Date Range when only one date is needed. |
|
Use the Date category for single-day values. |
| Using Duration instead of Date Range | You use Duration to represent a period with a fixed start and end. |
|
Use Date Range when both start and end dates are important. |
| Not tagging a calendar when business rules exist | You leave Tag Calendar as None even when holidays or working days matter. |
|
Link the field to a predefined calendar or the user’s calendar. |
| Using Date field to store timestamps for system events | You use Date or Date and Time for system-generated timestamps. |
|
Use auto-generated or system timestamp fields for event tracking. |