There’s a suggestion here:
It’s essentially to have a single table for all events you wish to display in the calendar. This master table will have an additional column used to identify the event type of each row which can then be used to generate sub-table views.
I.e. you have as many table views as you like, each containing events specific to that view (as identified by the type column) and then create the calendar from the master table.
Here’s an example:
- A project table holds two projects the team is working on
- A “hidden” project events table holds all the events
- Two views are created - one for each project. The project column itself is hidden.
- Two buttons are created to add new events for each project. Each button is configured to enter the right project name into the hidden project column.
It looks like two separate tables with one calendar but it’s really just one table with filtering.