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?
A couple of examples where this happens:
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.
Unfortunately that is the side effect. If each project needs to filter its own view, you are going to end up with a large number of view.
Looking for clarification, if you don’t mind.
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?
could you explain a little further?
In which table is this canvas column? And what is the table for which you create new rows in the canvas column?
Which is the main table? The table you have a view of in your page? The table with the canvas column, or another table?
It is best to prepare a doc with what you want to do, up to where you get stuck. Otherwise it is very difficult to assist.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.