This is a quite common use-case, for example when you want to visualize the tasks assigned to a project, within a canvas field of the project row containing a view of the tasks table.
The problem is that every time a project is created, a new tasks view is also created, so the number of connections to the original tasks table grows and grows. Is there any way to avoid that?
Could you explain why you want to avoid the creation of additional views?
That is the major benefit, that you can have multiple projects, and they all share the same task list. And that you can have project specific lists of the tasks related to that project.
It’s not that I want to avoid creating views, just wanted to avoid the clutter. In my use-case I am using this approach for tasks and subtasks, so it could easily reach hundreds of views.
Probably I don’t understand the coda data-model very well yet. The approach works, but I was hoping there would be a more elegant solution.
I have a page with a view of a table. If I use that page as the value for new rows in a canvas column, will rows created in the canvas column table view flow back up to the main table?
