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:
- Create a new table that contains both the vacation and sick leave data
- 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