Skip to content
Subtasks in Coda
  • Pages
    • Subtask Examples
    • Example One
    • icon picker
      Example Two
    • Example Three
Subtasks in Coda
/
Example Two
Share
Explore

Example Two

Two tables...connected!

This approach involves:

Two tables (one for your larger unit of work, one for the sub-items)
Connecting these two tables via a
relation column
⁠
⁠
Grouping
⁠
the tasks table by the project column

Table 1: Projects
Project Name
Owner
Status
Due Date
EcoBoost
1/31/2023
SmartHomes
2/15/2023
Cloud9
2/28/2023
There are no rows in this table
⁠
Table 2: Tasks
Project (relation column)
Task name
Task owner
Done?
3
Task A
Task B
Task C
3
Task D
Task E
Task F
3
Task G
Task H
Task I
⁠

light
Connecting tables in Coda with relation columns allows you to build docs more efficiently. Instead of writing all your project names again in the task table, a relation column lets you reference your list of projects that already exists in
Table 1: Projects
⁠
AND if you make a change to the name of one of these projects, that change will reflect in the relation column as well. Try it out.
light
Connecting tables via relation columns is not the same as creating a
view
⁠
of a table.
Relation columns are like a window to the rows of another table. We are “relating” a column to another table.
A View is a mirror of a table’s data that can be tailored to your unique needs, all while staying connected to the source.

Next →
Example Three
⁠

Gallery
 
Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.