# \[DONE\] Calendar DateRange & DateTime Range **URL:** \ **Category:** Bugs & Issues\ **Created:** [November 12, 2022, 12:48pm UTC](https://community.fibery.io/t/done-calendar-daterange-datetime-range/3529 "2022-11-12T12:48:46Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![rawkode](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rawkode/32/5317_2.png) [@rawkode](https://community.fibery.io/u/rawkode)\ **Post date:** [November 12, 2022, 12:48pm UTC](https://community.fibery.io/t/done-calendar-daterange-datetime-range/3529/1 "2022-11-12T12:48:46Z")
I have multiple entities and these entities each have either a DateTime Range or a DateRange. If I want to display them all on a calendar view, I can’t do it because of the type mismatch. I’d like to be able to see them all on a month view where the time part isn’t used. Could we make this possible, please? ---
**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:** [November 12, 2022, 3:10pm UTC](https://community.fibery.io/t/done-calendar-daterange-datetime-range/3529/2 "2022-11-12T15:10:36Z")
There are a couple of ways of doing this: - you can add a formula field for entities with DateTimeRange that just returns the date parts. then you can show them on the same calendar as entities that only have DateRange - vice versa: you can use a formula that adds times (maybe midnight to 23:59) for the entities with DateRange, so they can be shown with entities with DateTimeRange However, in both these cases, the entities will not be able to be moved on the calendar view (since the formula field is read-only and can’t be updated). A more sophisticated solution can be done, using standard fields and automations, which would allow entities to be moved within a calendar view, but in order to make an appropriate suggestion on how, it’d be good to know how you think users will/should interact with these entities. For example if a user changes the date of an entity on the calendar view, and this is an entity that uses DateTimeRange, what should the time values be? ---
**Author:** ![rawkode](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rawkode/32/5317_2.png) [@rawkode](https://community.fibery.io/u/rawkode)\ **Post date:** [November 12, 2022, 7:41pm UTC](https://community.fibery.io/t/done-calendar-daterange-datetime-range/3529/3 "2022-11-12T19:41:10Z")
This isn’t a solution, it’s a work around for something that should work out of the box. Calendar view shouldn’t care if it’s a Date, DateTime, or range. It should display my items, much like Google Calendar can do for “All Day Events” ---
**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:** [November 12, 2022, 10:08pm UTC](https://community.fibery.io/t/done-calendar-daterange-datetime-range/3529/4 "2022-11-12T22:08:58Z")
> [@rawkode](#): > > This isn’t a solution, it’s a work around for something that should work out of the box. Yep, 100% correct. This feature request of yours is the same thing, right? > [@\[DONE\] Allow Multiple Date Fields on Calendars](https://community.fibery.io/t/allow-multiple-date-fields-on-calendars/3154): > > I track conferences and my speaking sessions in Fibery (or i’m trying to) I can create a calendar to show both, however i need to ensure the date field is configured the same on both - which doesn’t really make sense for these fields. I’d like to be able to select multiple types and a date field for each, even when they differ slightly. Also, the “Only showing month” rule for dates without a time seems wild - can this be changed too? No time in dates: only month view will be available I m… ---
**Author:** ![rawkode](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rawkode/32/5317_2.png) [@rawkode](https://community.fibery.io/u/rawkode)\ **Post date:** [November 13, 2022, 3:56am UTC](https://community.fibery.io/t/done-calendar-daterange-datetime-range/3529/5 "2022-11-13T03:56:15Z")
Yeah, though I’ve decided this one small part of it is actually a bug. I can’t see why this distinction would be made. ---
**Author:** ![rawkode](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rawkode/32/5317_2.png) [@rawkode](https://community.fibery.io/u/rawkode)\ **Post date:** [November 25, 2022, 9:24pm UTC](https://community.fibery.io/t/done-calendar-daterange-datetime-range/3529/6 "2022-11-25T21:24:31Z")
Thank you for scheduling this > **[Roadmap Board](https://the.fibery.io/@public/Public_Roadmap/Roadmap-Board-5974#Roadmap_Item/Allow-to-show-Date-and-Date-Time-ranges-on-calendar-and-timeline-136)** > > Tailored workspace for your company. Connected databases, customizable views, powerful reports, automations, integrations, docs & whiteboards. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [December 15, 2022, 2:43pm UTC](https://community.fibery.io/t/done-calendar-daterange-datetime-range/3529/7 "2022-12-15T14:43:34Z")
Now you can do it ![Screenshot 2022-12-15 at 4.40.34 PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/4ba662aef7086116a264f49820fc4fb687108085.png) ---
**Author:** ![rawkode](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rawkode/32/5317_2.png) [@rawkode](https://community.fibery.io/u/rawkode)\ **Post date:** [December 17, 2022, 12:33pm UTC](https://community.fibery.io/t/done-calendar-daterange-datetime-range/3529/8 "2022-12-17T12:33:08Z")
Perfect 👍 Thanks ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [February 17, 2023, 9:49am UTC](https://community.fibery.io/t/done-calendar-daterange-datetime-range/3529/9 "2023-02-17T09:49:52Z")