The date/time field type is used to capture temporal data. As the name implies, this form field allows you to collect dates, times or a combination of date/time values. As with most of our form fields, the date/time field has a set of common properties that you can configure to control the field's behaviour and look.

We provide information on each individual property in the form designer itself. Click on the '?' icons to see detailed hints.

Here are some key aspects of the Date/Time field type:

Date/time type timezone implications

When selecting date/time options be mindful of timezone implications. These values can become complicated when you have users working in multiple timezones. Depending on your choice, our platform will store values in the local device timezone or the UTC/GMT timezone:

  • Date only stores values in local device timezone.
  • Time only stores values in local device timezone.
  • Date/Time stores values in UTC timezone.

Users should see the date/time values adjusted to their timezone in the data area of the secure website. If you want to set a user- specific timezone go to the navigation menu on the left and click on Organization & Users, then click User & Groups from the drop down. Hover over the desired user and click Edit User. You can specify the time zone under 'Regional Settings & Advanced Options'.

Date/time values in formulas and bound data sources

When working with date/time field answers in formula scenarios such as dynamic value, visibility, data source binding - be mindful of the above timezone implications for the fields in question. You can convert date/time values between local and UTC timezones using the DATETOLOCAL() and DATETOUTC() formula functions.

When inserting/updating rows in a data source with date/time values from a form you will see the values in the bound data source column are in UTC timezone. This is consistent with our platform policy of storing date/time values, and ensures your data source will work correctly when bound to date/time fields.

Date/time values stored in your local timezone

If you want a form to capture a date/time value in your local timezone, there are two options:

1. Use separate Date only and Time only fields instead of one Date/Time field. You can always combine these values later when utilizing them in templates or connectors.


2. Use a single Date/Time field, but add a hidden field that stores the local date/time equivalent value. This is done using the DATETOLOCAL() formula function in the hidden field's dynamic value property. Hidden fields store values in textual format. If you want to use this hidden field in a date formula e.g. DATEDIFF() you will need to convert the hidden field back into a date/time value via the DATE() formula function.

Did this answer your question?