# Calendar from multiple tables

**URL:** https://community.glideapps.com/t/calendar-from-multiple-tables/76595
**Category:** Ask for Help
**Created:** [September 24, 2024, 5:37pm UTC](https://community.glideapps.com/t/calendar-from-multiple-tables/76595 "2024-09-24T17:37:50Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![meganb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/meganb/32/16632_2.png) [@meganb](https://community.glideapps.com/u/meganb)
#### Post date: [September 24, 2024, 5:37pm UTC](https://community.glideapps.com/t/calendar-from-multiple-tables/76595/1 "2024-09-24T17:37:50Z")

</div>

I’ve seen other posts on this, and the repeated answer seems to be that the data needs to be compiled into one table. What I’m struggling with is that I have two tables that are set up with user specific favorite columns. Is it possible to compile user specific scheduling data into one table, so that it can all be displayed on one calendar?

---

<div class="post-metadata">

### Author: ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [September 24, 2024, 11:43pm UTC](https://community.glideapps.com/t/calendar-from-multiple-tables/76595/2 "2024-09-24T23:43:22Z")

</div>

What do you mean by “user-specific favorite columns” and “user-specific scheduling data”? Can you show us an example of your data structure and how the favorite columns come into play here?

---

<div class="post-metadata">

### Author: ![meganb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/meganb/32/16632_2.png) [@meganb](https://community.glideapps.com/u/meganb)
#### Post date: [September 25, 2024, 2:29pm UTC](https://community.glideapps.com/t/calendar-from-multiple-tables/76595/3 "2024-09-25T14:29:43Z")

</div>

Hi, yes, hopefully I can explain and show it in a way that makes sense. Probably 90% of the calendar data is being pulled from my “talks” sheet, but I have a small amount of events that are on my “overview” sheet. Each of these sheets has a favorites column that is set up with a user specific toggle, so our attendees can toggle the specific sessions and events they plan on attending.

Then I have a tab set up as “My Schedule.” So, this will use the user’s login email to identify which sessions they have marked on the “talks” sheet as favorites and show them in the calendar that I set up to display that collection.

I was trying to figure out a way to do it as a relational column somehow? But I couldn’t figure out what columns I should be trying to match? Or if a relational column would even work in the scenario of user specific columns?

 ![Screenshot 2024-09-25 at 10.26.34 AM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/f/4/f4db2538f96d6d52d4dc65428eb6b34512c848c4.png)  
 ![Screenshot 2024-09-25 at 10.26.48 AM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/4/d/4d8921265eac5b086441ce7d6e9d25bfa2cd3c92.png)  
 ![Screenshot 2024-09-25 at 10.20.42 AM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/3/4/343fe4736e92523f41bbe36cadd8cc0dd98b2bbc.png)

---

<div class="post-metadata">

### Author: ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [September 25, 2024, 11:59pm UTC](https://community.glideapps.com/t/calendar-from-multiple-tables/76595/4 "2024-09-25T23:59:52Z")

</div>

I think you can explore something like this:

- A query to get all “favorited” events from “Talks”.
- A query to get all “favorited” events from “Overview”.
- A lookup to get all favorited rowIDs from “Talks”.
- A lookup to get all favorited rowIDs from “Overview”.
- A Make Array column to join those two lookups into a single array of rowIDs.

> [@fishbaguette\_breadbasket Transpose Columns to an Inline List: The Miracle Method](https://community.glideapps.com/t/transpose-columns-to-an-inline-list-the-miracle-method/32766):
>
> I’m often asked how to take columns of data (say form responses) and display them in an inline list. Here’s one way to do it—the MIRACLE METHOD. [[Glide: Transpose Data Columns into an Inline List with the MIRACLE METHOD] ](https://www.youtube.com/watch?v=t-sh_Q3WbQc)

Use this method to transpose that list of IDs in a new helper table. Add as many rows as you might need.

- Use two relations to try to link each rowID back to their “Talks” and “Overview” table.
- Use lookups to pull over titles, start times and end times from each relation.
- Use if-then-else columns to get the final titles, start times and end times (since only one from each pair of columns for those can contain a value).
- Use those values for your Calendar.

---

<div class="post-metadata">

### Author: ![meganb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/meganb/32/16632_2.png) [@meganb](https://community.glideapps.com/u/meganb)
#### Post date: [September 27, 2024, 3:29pm UTC](https://community.glideapps.com/t/calendar-from-multiple-tables/76595/5 "2024-09-27T15:29:16Z")

</div>

Eeek, this one might be way over my head. A thought I just had though was that it feels like it should, in theory, be possible to use the users table as the source data for the calendar? But, there is no specific column on the user table that I can use to display the favorited sessions, even though shouldn’t all of that data be tied to the user’s profile?

---

<div class="post-metadata">

### Author: ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)
#### Post date: [September 28, 2024, 2:23am UTC](https://community.glideapps.com/t/calendar-from-multiple-tables/76595/6 "2024-09-28T02:23:35Z")

</div>

It does tie to the user, but it still comes from different tables, so you still have to go through the steps above to bring them to the same helper table.
