# Allow changing the field type from DateTime → Date **URL:** \ **Category:** Ideas & Features\ **Tags:** flexible-domain\ **Created:** [March 24, 2026, 4:06pm UTC](https://community.fibery.io/t/allow-changing-the-field-type-from-datetime-date/10642 "2026-03-24T16:06:13Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![ID.000](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/id.000/32/14109_2.png) [@ID.000](https://community.fibery.io/u/ID.000)\ **Post date:** [March 24, 2026, 4:06pm UTC](https://community.fibery.io/t/allow-changing-the-field-type-from-datetime-date/10642/1 "2026-03-24T16:06:13Z")
We ran into a limitation while working with **Date fields that include time**. Our team works across multiple time zones, and we noticed that storing **date + time** sometimes creates inconsistencies in how entities appear for different users. Because of this, we decided that for this field we only need the **date without time**. However, Fibery currently does not allow switching a Date field from **date & time → date only**. From a practical standpoint, it would be very helpful if this conversion were still allowed. **Suggestion:** Allow changing the field type from **DateTime → Date (no time)** even when time values exist, but show a clear warning such as: > “Time values will be removed from existing records.” The reason this is important is that this field is already used in **many formulas and automations** in our workspace. At the moment, the only workaround is to: 1. create a new field 2. migrate all data 3. update every formula and automation that references the old field This becomes quite time-consuming and error-prone in larger workspaces. Allowing the field type conversion with a warning would make schema adjustments much easier without breaking existing workflows. --- _[View the full topic](https://community.fibery.io/t/allow-changing-the-field-type-from-datetime-date/10642)._