Help

The Community will be undergoing maintenance from Friday February 21 - Friday, February 28 and will be "read only" during this time. To learn more, check out our Announcements blog post.

Re: Link interface to more than one tab

Solved
Jump to Solution
50 0
cancel
Showing results for 
Search instead for 
Did you mean: 
Country_Pigeon
5 - Automation Enthusiast
5 - Automation Enthusiast

Hello - I'm fairly new to Airtable and I have a base with 5 tables, each table contains the schedule of a different project that I am tracking.  I want to create an interface calendar that displays milestones across the 5 projects, but I can only see how to source from one table.

Is there a way to connect your interface to more than one table? Thank you in advance for any help!

1 Solution

Accepted Solutions
DisraeliGears01
7 - App Architect
7 - App Architect

Short answer is you can build an interface page that spans multiple tables using the Blank page option. It'll take a bit more construction than a simple calendar page, and your tables will be contained on different calendar widgets, but it'll all be the same interface page.

If getting all the project info on to one calendar widget is the goal, you can either restructure your data so there's one project table, with each row being a project interlinked to other tables (better for long term data structure anyway probably) or you can create a junction table and use lookup fields to get all your necessary info into one table to use for an interface.

See Solution in Thread

4 Replies 4
DisraeliGears01
7 - App Architect
7 - App Architect

Short answer is you can build an interface page that spans multiple tables using the Blank page option. It'll take a bit more construction than a simple calendar page, and your tables will be contained on different calendar widgets, but it'll all be the same interface page.

If getting all the project info on to one calendar widget is the goal, you can either restructure your data so there's one project table, with each row being a project interlinked to other tables (better for long term data structure anyway probably) or you can create a junction table and use lookup fields to get all your necessary info into one table to use for an interface.

Country_Pigeon
5 - Automation Enthusiast
5 - Automation Enthusiast

Thank you!😀

If the data is restructured so that there is one table with each row interlinked to other tables, would the row be a roll-up of specific fields within the detailed project schedule table it is linked to? I'm not sure what this would look like - if you are able to explain further I would be very appreciative. 

In an ideal world, you'd have all 5 of your projects in the same table, one for each row, with fields for title, description, start/end date, etc. Then you'd have a linked record field to a new table for "Tasks" or something similar, which breaks down the project into constituent parts. Then you can use lookup or rollup fields to move the data from Tasks into Projects, and map it to a calendar view. There are several project management templates Airtable has that break down like this.

From that general concept, you can make modifications. If your projects aren't start/end, but full of recurring tasks, you can set up your task table differently etc. Now if your projects are vastly different with large datasets (analytics tracking vs marketing material creation, etc) then perhaps multiple tables or bases is the right approach, but usually you want to gather like together.

Country_Pigeon
5 - Automation Enthusiast
5 - Automation Enthusiast

Thank you, @DisraeliGears01 . This makes sense. I do have a Project table that is linked to each schedules end date, and I had planned on adding more roll-up items as the schedules are created, but the projects are different enough that they, unfortunately, may need to be on separate tables. 

I appreciate your time and expertise!!!