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 remaining 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 (and under the same column(s) if there are 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.
table that have “Start” and “Deadline” columns. Calendars in Coda require that all events have a start and end date in order to accomplish this. So we add another column, “Event Start” for all rows, which together with the “Date” column will serve as the start and end dates for the calendar. The “Event Start” is the same date as the “Start” column for rows coming from the
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.