Syncing tables across bases--help needed

[wmlutz]

I've seen iterations on this question, but never an answer that works for my case.

I have a base for newsletter management. Two tables in the base (others omitted for clarity), one to track and manage the weekly newsletter (author, topics, etc.) and one for events and holidays in our community.

I'd like to put them together into a master calendar. I have been trying to do it at the field/formula level on a new table, but can't figure it out. I only need two fields, the date of the entry, and a subject or name field.

I think I could solve this if I could get a calendar view to subscribe to another calendar view's exported iCal URL, but I can't figure out how to do that either.

Any help?

[Alexey_Gusev]

Hi,
You can create a master table for calendar and link to these 2 tables, using their data via lookups.
More simple solution is to put all data in the same table, add single select type of event and use different views for newsletter and events&holidays.
Primary field might be a formula with date, event type and something else, to distinguish different records.

[TheTimeSavingCo]

If you're on a Business or above plan you could also try syncing those two tables into a single table in another base

[ScottWorld]

Here are a few options: (1) You can use syncing to sync both tables to a unified table in another base, or (2) you can sync externally to a calendar app like BusyCal for Mac, or (3) you can use the Master Calendar extension in Airtable which will display a calendar with records from different tables combined onto one calendar.

— ScottWorld, Expert Airtable Consultant 

[Alexey_Gusev]

Yes, they can be synced. I also did the sync of several tables to the same base, using another base as 'mirror' to sync them back. 

Such syncing instead of just holding data in the single table can cause troubles as soon as you want to put automations triggered by the synced table. Because you can make changes in source tables only. If you want to put automation in source tables, each automation must be repeated multiple times according to a number of tables. And each change must be repeated in other(s). I supported this config 2 or 3 months, and then I get tired of all those issues, and turned it back to a single table.