# Calendar view with multiple fields from same database

**URL:** <https://community.fibery.io/t/calendar-view-with-multiple-fields-from-same-database/5691>\
**Category:** Get Help\
**Created:** [January 15, 2024, 3:29pm UTC](https://community.fibery.io/t/calendar-view-with-multiple-fields-from-same-database/5691 "2024-01-15T15:29:16Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![gomocoop](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/gomocoop/32/6349_2.png) [@gomocoop](https://community.fibery.io/u/gomocoop)\
**Post date:** [January 15, 2024, 3:29pm UTC](https://community.fibery.io/t/calendar-view-with-multiple-fields-from-same-database/5691/1 "2024-01-15T15:29:16Z")

</div>

I have a database which the entities have three different date fields that I wanted to show on the same calendar view. But when I choose ITEMS it will only allow me to use each database once…

Is it possible to show more then one field from the same database/entity in the same calendar?

---

<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:** [January 15, 2024, 3:33pm UTC](https://community.fibery.io/t/calendar-view-with-multiple-fields-from-same-database/5691/2 "2024-01-15T15:33:27Z")

</div>

> [@gomocoop](#):
>
> Is it possible to show more then one field from the same database/entity in the same calendar?

Nope. Not currently possible

---

<div class="post-metadata">

**Author:** ![gomocoop](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/gomocoop/32/6349_2.png) [@gomocoop](https://community.fibery.io/u/gomocoop)\
**Post date:** [January 15, 2024, 4:01pm UTC](https://community.fibery.io/t/calendar-view-with-multiple-fields-from-same-database/5691/3 "2024-01-15T16:01:00Z")

</div>

Oh, 🥲

Is it in the development horizon anyhow?

---

<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:** [January 15, 2024, 4:07pm UTC](https://community.fibery.io/t/calendar-view-with-multiple-fields-from-same-database/5691/4 "2024-01-15T16:07:44Z")

</div>

It’s not planned, or in the backlog anywhere as far as I know.  
What’s the use case for showing something twice in the same view?

---

<div class="post-metadata">

**Author:** ![gomocoop](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/gomocoop/32/6349_2.png) [@gomocoop](https://community.fibery.io/u/gomocoop)\
**Post date:** [January 15, 2024, 5:50pm UTC](https://community.fibery.io/t/calendar-view-with-multiple-fields-from-same-database/5691/5 "2024-01-15T17:50:58Z")

</div>

I work with people management and we have different roles, so I created and entity for each role.

Every role has 3 performance review meeting dates.

 ![Captura de Tela 2024-01-15 às 14.49.40](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/03151e07524f3f8124ca93a04fb563bf1ff90cdb.png)

So I wanted to see those 3 dates from every role on the calendar. It wouldn’t be showing twice.

---

<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:** [January 15, 2024, 5:59pm UTC](https://community.fibery.io/t/calendar-view-with-multiple-fields-from-same-database/5691/6 "2024-01-15T17:59:40Z")

</div>

Thanks for the use case clarification, and sorry for writing _twice_ when it should have been _thrice_(!)

---

<div class="post-metadata">

**Author:** ![gomocoop](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/gomocoop/32/6349_2.png) [@gomocoop](https://community.fibery.io/u/gomocoop)\
**Post date:** [January 15, 2024, 6:14pm UTC](https://community.fibery.io/t/calendar-view-with-multiple-fields-from-same-database/5691/7 "2024-01-15T18:14:20Z")

</div>

Hahaha yes, but I mean it’s not showing something twice or thrice because it’s not the same thing. Right?

---

<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:** [January 15, 2024, 7:05pm UTC](https://community.fibery.io/t/calendar-view-with-multiple-fields-from-same-database/5691/8 "2024-01-15T19:05:34Z")

</div>

Well, I just meant that you wanted to a role to be shown on the calendar on three different dates (if I understood you correctly)

---

<div class="post-metadata">

**Author:** ![njyo](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/njyo/32/923_2.png) [@njyo](https://community.fibery.io/u/njyo)\
**Post date:** [January 16, 2024, 2:03am UTC](https://community.fibery.io/t/calendar-view-with-multiple-fields-from-same-database/5691/9 "2024-01-16T02:03:07Z")

</div>

I think a clean solution that works would be to generate actual meetings for the dates for each role and then place the meetings in the calendar. Also allows you to move them or repeat them next round. 🙂

---

<div class="post-metadata">

**Author:** ![gomocoop](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/gomocoop/32/6349_2.png) [@gomocoop](https://community.fibery.io/u/gomocoop)\
**Post date:** [January 16, 2024, 12:09pm UTC](https://community.fibery.io/t/calendar-view-with-multiple-fields-from-same-database/5691/10 "2024-01-16T12:09:36Z")

</div>

Oh! That’s simple and quite interesting actually! \<3

I’ll go for that for now, thanks!

---

<div class="post-metadata">

**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:** [November 10, 2025, 3:11pm UTC](https://community.fibery.io/t/calendar-view-with-multiple-fields-from-same-database/5691/11 "2025-11-10T15:11:49Z")

</div>

We have a use case for this. Each time we release a set of tickets (an on-sale) for events there are multiple sets of dats related to it and we want to show them all on a calendar view without having to have too many entities:

- Priority Access DateTime
- Public Access DateTime
- Sold Out DateTime
