# Time only fields **URL:** \ **Category:** Ideas & Features\ **Tags:** flexible-domain\ **Created:** [May 23, 2025, 7:50pm UTC](https://community.fibery.io/t/time-only-fields/8851 "2025-05-23T19:50:20Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![danielbmarsh](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/danielbmarsh/32/13104_2.png) [@danielbmarsh](https://community.fibery.io/u/danielbmarsh)\ **Post date:** [May 23, 2025, 7:50pm UTC](https://community.fibery.io/t/time-only-fields/8851/1 "2025-05-23T19:50:20Z")
I have run into many use cases where I don’t need the date associated with a time field. Why because the entity itself is already associated with a day, or the is no day associated with the time. I will give some examples: I am building a weather integration that automatically pulls in weather data. There are 3 databases that exists in the integration (Location, Day, Hour). - Location entity is tied to a script that pulls in day and hour weather details for a given place - Every Day Entity is associated with a date (e.g. Jan 1, 2025), and connected to a location. - Every Hour Entity is linked to a day. There are 24 linked to every day With this structure I can now report on daily weather data and hourly weather data. On the daily weather data I have fields such as Sunset and Sunrise. It seems pointless to select the day at that time as it is already associated with a day. Another example I am building a scheduling system. In it I need users to define their availability on a given day of the week. The users will select the time ranges they are free Sunday - Saturday. A date with this is completely irrelevant. Note there are work arounds. I can use text fields or single select fields to resemble a time. ---
**Author:** ![Lee\_Denny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lee_denny/32/8158_2.png) [@Lee\_Denny](https://community.fibery.io/u/Lee_Denny)\ **Post date:** [May 26, 2025, 2:11pm UTC](https://community.fibery.io/t/time-only-fields/8851/2 "2025-05-26T14:11:59Z")
would also find this very useful ---
**Author:** ![bear](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bear/32/12872_2.png) [@bear](https://community.fibery.io/u/bear)\ **Post date:** [October 14, 2025, 7:56am UTC](https://community.fibery.io/t/time-only-fields/8851/3 "2025-10-14T07:56:05Z")
My client wants his employees to log the starting and ending time of work at a customer, so he can calculate how long they were there. His employees are working from their phones. It is a hassle to fill in the date every time (pun not intended 😉). Can ‘exclude date’ be added as an option for the Date field so it just becomes a time field or can a Time field be added? Or is there another workaround to do this? ---
**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\ **Post date:** [October 14, 2025, 12:38pm UTC](https://community.fibery.io/t/time-only-fields/8851/4 "2025-10-14T12:38:07Z")
Not the same, but related issue, especially if considering modifying the existing date field capabilities: [More Flexible Date FIeld](https://community.fibery.io/t/more-flexible-date-field/2481/) ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [February 12, 2026, 3:34pm UTC](https://community.fibery.io/t/time-only-fields/8851/5 "2026-02-12T15:34:38Z")
A post was merged into an existing topic: [Add Duration as a valid field type](https://community.fibery.io/t/add-duration-as-a-valid-field-type/3710/4) ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [February 12, 2026, 12:53pm UTC](https://community.fibery.io/t/time-only-fields/8851/6 "2026-02-12T12:53:53Z")
i believe these can be merged. [Add Duration as a valid field type](https://community.fibery.io/t/add-duration-as-a-valid-field-type/3710) ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [February 12, 2026, 1:48pm UTC](https://community.fibery.io/t/time-only-fields/8851/7 "2026-02-12T13:48:43Z")
I don’t think so. I think duration field is equivalent to ‘date timeA - datetimeB’ (expressed in whatever units are appropriate) so it could be e.g. 47 mins, whereas time field is just a fixed point within a 24hr period, e.g. 11:13:26 (13 mins and 26 seconds past 11 o’clock). They could become functionally equivalent e.g. by setting datetimeB to always be midnight on the date of datetimeA, but I think overall they serve different purposes. I’d like to collect use cases for each of them separately. ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [February 12, 2026, 3:25pm UTC](https://community.fibery.io/t/time-only-fields/8851/8 "2026-02-12T15:25:20Z")
Ah, I think we see this differently. > [@Chr1sG](#): > > I think duration field is equivalent to ‘date timeA - datetimeB’ (expressed in whatever units are appropriate) What you mention here, I have thought of as a way of formatting a calculation. I.E. changing the format on a datetime field to only show the time formatted as 00:00 I’ve often assumed that time fields without a date allow us to enter in time in 1 denomination (say hours) and it is stored on the server as another (say seconds) then rendered in a variety of formats - this is what you call a fixed point. Although I would add that if this was the method, the time could extend past 24hrs. That said, whether Fibery adds time as a format option to existing datetime fields, it does make sense that time without a date value might need a different field type.