DateTime Field
The GravityWP - DateTime Field add-on adds a dedicated Date/Time field to Gravity Forms so users can enter both a date and a time in a single input.
The GravityWP DateTime Field add-on adds a dedicated Date/Time field to Gravity Forms so users can enter both a date and a time in a single input.
Instead of splitting the experience across separate fields, you collect one combined value, apply Not before and Not after limits, and use merge tags to create dynamic rules between fields. In testing, the field accepted valid values, rejected values outside the allowed range, and handled field-to-field validation such as preventing an End Date and Time from being submitted earlier than a Start Date and Time.
Features
- Single Date and Time Field
Add one field that captures both the date and the time in a single input. This keeps forms cleaner and makes scheduling-based forms easier to build and easier to complete. - Date/Time Limits
Set the earliest allowed value with Not before and the latest allowed value with Not after, directly inside the field settings. Works for fixed windows like booking deadlines and open-ended scheduling alike. - Merge Tag Support in Limits
Use merge tags inside the limit settings to create dynamic, field-to-field rules. In testing, setting an End Date and Time field’s Not before value to the Start Date and Time merge tag correctly prevented users from submitting an end value earlier than the start. - Clear Validation Messages
When a submitted value falls outside the allowed range, the field returns a clear validation message telling the user exactly what date/time is required no guessing, no silent failures. - Consistent Submitted Value Submitted values are returned as a single combined date/time string in this format:
YYYY-MM-DD HH:MM:SS - That makes the field immediately practical for confirmations, notifications, scheduling logic, and any downstream workflow that depends on one clean, consistent value.
How It Works
Add the Date/Time field to your Gravity Form, then open its field settings to configure the allowed range.
Enter a fixed value in Not before and Not after when you want a simple booking window or a submission deadline. Insert a merge tag when the allowed date/time should depend on another field in the same form.
For example if your form has a Start Date and Time field and an End Date and Time field, set the End field’s Not before value to the Start field’s merge tag. From that point on, users cannot submit an end value earlier than the start. The form validates this on submission and blocks it with a clear message if the rule is broken.
This makes the add-on the right fit for appointment forms, booking forms, event scheduling, deadline submissions, and any workflow where the order of date/time values matters.
GravityWP Date Time Field – FAQ
It adds a dedicated Date/Time field to Gravity Forms so users can enter both a date and a time in one input, with optional limits and merge-tag-based rules to control what values are accepted.
Yes. The field includes Not before and Not after settings so you can define the earliest and latest allowed value directly from the field settings in your form builder.
Yes. In testing, merge tags worked correctly in both limit fields including a field-to-field rule where an End Date and Time field could not be submitted earlier than a Start Date and Time field.
The form shows a validation message and blocks submission until the entered value falls within the allowed range.
Yes. A tested use case was a form with a Start Date and Time field and an End Date and Time field, where the end field used the start field’s merge tag as its minimum allowed value. It worked as expected in testing.
Submitted values appear as: YYYY-MM-DD HH:MM:SS
Appointment forms, booking forms, event registration forms, scheduling forms, and deadline-based forms any workflow where users need to choose both a date and a time, and where the order or range of those values needs to be enforced.