# Option to filter on "time" from entity's datetime in month view

**URL:** <https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235>\
**Category:** Ideas & Features\
**Created:** [October 2, 2023, 1:03pm UTC](https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235 "2023-10-02T13:03:17Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\
**Post date:** [October 2, 2023, 1:03pm UTC](https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235/1 "2023-10-02T13:03:17Z")

</div>

Would be nice to have the option to show just time from the datetime of entities in the month display of a calendar view.

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [October 2, 2023, 2:29pm UTC](https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235/2 "2023-10-02T14:29:00Z")

</div>

Related: Although the below post is specifically about Grid view, it actually applies to all views:

> [@Customize which entity fields (units) are displayed in Grid View relation columns](https://community.fibery.io/t/customize-which-entity-fields-units-are-displayed-in-grid-view-relation-columns/5219/1):
>
> it would be super useful to be able to customize which fields are displayed for each entity (instead of only the entity Name).

---

<div class="post-metadata">

**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:** [October 2, 2023, 2:36pm UTC](https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235/3 "2023-10-02T14:36:29Z")

</div>

You can extract the time from the datetime field using a formula. Obviously not as good as an editable field, but if you just need to show the time as a field on a card, maybe it’s good enough.

---

<div class="post-metadata">

**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\
**Post date:** [October 2, 2023, 3:08pm UTC](https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235/4 "2023-10-02T15:08:16Z")

</div>

I’m having trouble seeing how I would do that with the function options provided - code you provide a pseudocode example?

---

<div class="post-metadata">

**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:** [October 2, 2023, 3:22pm UTC](https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235/5 "2023-10-02T15:22:34Z")

</div>

`Middle(ToText(Date), 12, 5)`

---

<div class="post-metadata">

**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:** [October 2, 2023, 3:23pm UTC](https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235/6 "2023-10-02T15:23:50Z")

</div>

FYI this topic’s title mentions filtering, but in the body text you just talk about showing the time, so I hope I understood the need correctly.

---

<div class="post-metadata">

**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\
**Post date:** [October 2, 2023, 4:52pm UTC](https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235/7 "2023-10-02T16:52:20Z")

</div>

Awesome. I added .Start and .End values and a “-” to recreate the look of a time range. I’m running into the UTC issue others have mentioned elsewhere though, but let me elaborate.

The “Date” being converted in the ToText() function is the date range field from a google calendar integrated event. When I convert to text, I get back the UTC value and since it’s text, Fibery isn’t using my browser’s time zone to update the time value, so I’m stuck with UTC time text. Any ideas on how to get the time back as text in my local time zone?

---

<div class="post-metadata">

**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:** [October 2, 2023, 5:27pm UTC](https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235/8 "2023-10-02T17:27:40Z")

</div>

You could add/subtract an offset prior to convert to text, but there would still be issues with summer/winter time.  
[Timezones are tricky](https://the.fibery.io/@public/User_Guide/Guide/Timezones-41)

---

<div class="post-metadata">

**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\
**Post date:** [October 2, 2023, 6:28pm UTC](https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235/9 "2023-10-02T18:28:48Z")

</div>

Okay maybe I can create some sort of conditional for the offset that adjusts by one offset value for half the year and another offset for the other half if I can figure out how to access second Sunday of March and first Sunday of November in the formula.

---

<div class="post-metadata">

**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\
**Post date:** [October 2, 2023, 6:30pm UTC](https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235/10 "2023-10-02T18:30:03Z")

</div>

Also re: filtering I meant filter just the time from the date range value, but I think we’ve gotten the best solution given the existing Fibery capabilities.

---

<div class="post-metadata">

**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:** [October 2, 2023, 6:41pm UTC](https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235/11 "2023-10-02T18:41:30Z")

</div>

> [@tycecycle](#):
>
> maybe I can create some sort of conditional for the offset that adjusts by one offset value for half the year and another offset for the other half if I can figure out how to access second Sunday of March and first Sunday of November in the formula.

It is almost certainly possible to write a formula that calculates when the switch occurs, but I’m guessing it won’t be pretty!

---

<div class="post-metadata">

**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:** [October 2, 2023, 6:55pm UTC](https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235/12 "2023-10-02T18:55:19Z")

</div>

> [@tycecycle](#):
>
> Okay maybe I can create some sort of conditional for the offset that adjusts by one offset value for half the year and another offset for the other half if I can figure out how to access second Sunday of March and first Sunday of November in the formula.

I could imagine it might actually just be easier to create a database containing the dates of the switches to/from DST (a pair of dates for each year). Then you can auto-link all your entities to the relevant dates based on matching the year of the entities, and it would become much easier in a formula to then determine how many hours to offset.

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [October 2, 2023, 8:01pm UTC](https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235/13 "2023-10-02T20:01:50Z")

</div>

I would humbly suggest this might be work that Fibery “should” be doing for users in much the same way as the “World” and Currency Exchange “integrations” work…

---

<div class="post-metadata">

**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:** [October 2, 2023, 8:54pm UTC](https://community.fibery.io/t/option-to-filter-on-time-from-entitys-datetime-in-month-view/5235/14 "2023-10-02T20:54:02Z")

</div>

Maybe, but we’re back to the ‘timezones problem’. Given that a workspace can be accessed by multiple users, who may be spread across different timezones, there is no single correct value for ‘local time’.  
Formulas are always calculated on the backend, so can’t return different values for different users.

I would imagine that the more likely solution is for Fibery to support a ‘time’ datatype (together with the functions needed to extract time from datetime / combine date + time to form datetime).  
In such a situation, the UI rendering would take into account converting to ‘browser time’.

It’s all part of a large pandora’s box of issues that need to be addressed in service of ‘localisation’.
