Combine two different table data in one calendar view

Ah at this point Calendar Interface layouts can only display data from a single table I believe

To achieve what you’re looking for I think you’d need to either:

1. Create a new table that contains both the vacation and sick leave data
2. Create the sick leave data in the vacations table

For both, you’d populate them via automations and create lookups and formula fields to consolidate the data for the Interface to display

Hopefully someone else has a better idea!

---

Is there any chance you could use the same table for both the Vacation and Sick data instead?  If you had a ‘Type’ single select field to designate what type of data each record was (vacation or sick) then the Calendar would work right out of the box and it’d be a lot cleaner

Hey ​@Philip_Klimaten,

As mentioned above, that is not possible. Furthermore, except for very specific use cases where you might want to split your data in different tables, if they represent the same object/entity (i.e. at the end of the day, Vacation and Sick data seem to be both “events” sharing many attributes/fields) you’ll really want to have them under one unique table.

If you’d like to go through this together on a quick call I’d be happy to show you around database best practices :D

Mike, Consultant @ Automatic Nation 
YouTube Channel

Hi ​@Philip_Klimaten! 

Cleanest solution is ​@TheTimeSavingCo Adam’s #1 solution, i.e. try to melt both form submissions / use cases into using the one table (which, down the track, you may need to add in a third, fourth, etc use case into).

Alternatively, if you are on Business Plan or above, there’s a trick you can do with multi-source sync:

• Create another base
• Sync in one of the tables
• Multi-sync in the other table, into that first table
• (You can repeat this to layer up to 20 ‘similar’ data sources)
• Then sync this ‘stacked’ table, back into your original base
• Use THAT as the basis of your calendar view.

You won’t be able to edit details inside the calendar view, but it’s a pretty handy way to show dates / records from different tables in a single view / interface / timeline etc.