Skip to content
Gallery
Merge Table Pack
Share
Explore
Demo

icon picker
Union merge

A more complex demo which merges tasks, meetings, and projects, to view the task due dates, meeting dates, and project start-to-deadline spans together in a single calendar
thick-arrow-pointing-down

Jump to at the bottom of the page to see the magic ✨

info

Tables in this demo doc are not editable, and the doc cannot be copied. Check out the starter template version of this demo instead:

The below sync table merges rows from the table, table, and table onto the union of the columns of each table.
Merge table details
The “Merged Row” column is a special sync table row representing the merged row itself, and the “Table Name” column is another pack-created column representing metadata about the merged row. These columns can be hidden.
The rows are grouped based on which table they were merged from, but you could un-group them.
All columns are shown, but you could hide or delete them.
Union merging details
With union merging, the resulting columns are those in any of the tables included to be merged, and their values are those of all the rows of all tables, under these columns (merged under the same column(s) for any common column(s)).
Since we are using union merging, some columns are not common to all tables included to be merged, and so they are blank for rows coming from tables that do not share those columns.
Tasks + Meetings + Projects
2
In the view, we add a column to prefix the row name with an emoji to differentiate events in the . We add another column to show dates for rows from the table that span from their “Start” to “Deadline” columns.
Added columns details
We want to be able to distinguish events in the calendar based on which table they come from, so that we can tell apart , , and . So we add a column, “Event name” that adds an emoji to the row name to represent the type of event, and set it as the display column for the calendar.
We want the calendar to show dates for events that span multiple days, for rows from the table that have a “Start” and “Deadline” column. Calendars in Coda require that all events have a start and end date in order to accomplish this (rows with the same “Event start” and “Event end” will appear as single-day events).
We add an “Event start” column to the Merge table, which will serve as the start date for the calendar view. The “Event start” is the same as the “Start” column for rows coming from the table, and the same as the “Date” column for rows coming from the and table.
The Merge table already has a “Date” column, which will serve as the end date for the calendar view. The “Date” column is included in all the source tables. For and tables it is a hidden helper column which is the same as the “Due date” and “Deadline” columns (for the table, its column is simply named “Date”, since deadlines don’t really make sense for meetings.)
With a few additions to the Merge table we get a clear visualization of all project-related events as a single calendar in our view.
Enriched view of Tasks + Meetings + Projects
2
Calendar view of Tasks + Meetings + Projects
2

October 2024

Month
Today
Sunday
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
🎯 Marketing Pages
🎯 Android App
🤝 Design mock review
🎯 Marketing Pages
🎯 Android App
🎯 iOS App
✅ App development
🤝 App development design session
🎯 Marketing Pages
🎯 Android App
🎯 iOS App
✅ Design mock approval
✅ QA + bug squashing
🤝 App design planning
🎯 Android App
✅ App design - iOS
🎯 iOS App
✅ Create launch promotion plan
✅ App design - Android
🤝 QA bug squash session
The calendar view neatly merges together all the , , and .
From each event in the calendar you can easily navigate back (hover over the event then click the link) to the actual row in its table somewhere else in the doc to get the full picture or make edits to the source.
The calendar can be kept in sync automatically, and refreshed on-demand.
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.