I’m looking to build a master table that I can filter to a project while editing the status of the tasks. The problem I’m facing is that my tasks table can change (grow and shrink) and I want each project to reflect those changes automatically.
I see threads that show solutions similar to what I’m hoping for with FormulaMap and AddRow, but these solutions appear to be a one time thing, and re-add all rows upon clicking again.
Does anyone have a strategy to accomplish this? Appreciate your thoughts!
@Joshua_Upton, thanks for the reply. I requested access to the doc you shared (I can’t see it!).
I can understand how what I posted might be a bit ambiguous; the point that’s unique vs templates: Every project has the same set of tasks, and periodically, that set of tasks might change.
For example:
Project A
The whole tasks table
Project B
The whole tasks table
If I were to add a task to the Tasks table, I would expect both Project A and Project B’s set of tasks to increment with the same task, projects to no longer be complete, so I can manually mark the task complete for each project as they’re completed.
I hope that makes sense, and in all likelihood I’m digging into just one possible solution – I am absolutely open to a better way to accomplish this.
Hi @Joshua_Upton – thanks for sharing that doc. I’m not sure it’s quite what I’m hoping to achieve; for example, switching projects and filtering the Master table works, and I understand that much, but each project has only a subset of the tasks, whereas I want to join all tasks onto each project.
Here’s an example of the functionality I’m ultimately looking for:
In the above screenshot, every project has every task, and they’re all complete. However, if I were to add a new task into the mix:
Now I’ve added that task for each project.
I could just add columns for each project in the tasks table within Coda, but that eliminates any benefit of storing projects in their own table since I don’t see a way to do anything dynamically with columns (including with Actions which seem primarily row-driven).
Still struggling to find a scalable solution for this, even if it’s different than how I was envisioning it. Has anyone had similar needs where every row of a table requires an entire view of another table unique to it?
Any official Coda folks out there willing to give this a once over?
@Saul_Garcia Yes! That looks exactly right – it might take me a bit to unpack exactly what’s going on in there but that is the exact functionality I was hoping Coda could handle – even with a pivot! Thank you!
