I have a 50 item checklist we have created. The to do items are listed in rows with all the usual tracking and to do items, etc. My question is what is the best way to use it across multiple projects in one database? Right now I can see how you could copy template and create a new table from each project from the blank template and then if needed consolidate them all into another table but since this template will grow all the time it won’t update into older projects if I make changes to the newest table. Would love to know if others have come up with interesting ways to conquer this one. I know how to filter it properly to show one project at a time to show different views based on projects but that is not really what I want.
Thanks for good ideas
You could create a dedicated table that pulls/copies from the source (the 50-item checklist), and each time you have a project, via a button, you can add a fresh copy of those 50 items so that whenever you mark an item from the checklist (per project) as done, then it doesn’t update for all projects (kinda like subitems/subtasks).
Do I understand correctly that you want for each project a 50 item checklist?
And do you want to be able to change the checklist items in such a way that new and old tables show the changes.
And what about adding more checklist items - or deleting some items. Should that also be represented in old projects?
As has been said in this community, if you want the community to put effort into helping you, the least you could do yourself is make and share a dummy doc the shows (and tells) as good as possible what you want to accomplish. I think what you want to do can be done with automations formulas, but I, and I think more of us, don’t want to waste our time trying to guess what it is that you are trying to accomplish.
The reason I haven’t gone into details is because this is a conceptual structure question – something that I imagine others have considered. It’s about how to manage something when the rows are more like columns in that they are what is being tracked across a project. But having a checklist in a landscape mode is not practical when the volume of checklists is so many.
If I could put my rows in columns it would be very straightforward. So the details of my project in this case are not relevant. In fact, I haven’t built it because I am looking to see if anyone has approached this problem in a way that I could consider before jumping into an architecture that doesn’t work.
I hope that helps.
Hello @Chris_DeAngelis ,
Coda has so many ways to organize this type of data and I think I have run (and solved) this type of problem in the past with multiselect relational columns, multiselect select columns. With relational columns you can ‘embed’ the relational table (with filters) and accomplish what I think you are after.
Unfortunately, without some sort of a draft, dummy doc or better explanation from you it is (for me) impossible to help you any further.
Greetings,
Joost
I’ve had to do that recently and I’ve got a working documents. I have 4 people using it. and now it feels like I’ve created a monster…
Current context:
Team has multiple processes based on client type or deal type.
I have created a table of task templates that are mapped (relation) to Client types or Deal types
- So any task that may apply to a client type is mapped to type using multi-select relation
I have a client table and a deal table
Team member adds a new client, selects the type of client when done, a button enables to generate the tasks.
Now each client row and deal table have all relevant subtasks to do listed and ready to be ticked
Happy to share or demo
Hey Chris,
Not sure if still working on this.
Have you considered just having one master table that is the home for the checklist for all projects.
Then have a column for project as a way to filter the view based on current project.
Avoids having duplicated and customised tables that are impossible to maintain with any changes.
Chris
Nice solution. Is the button one button per task or does it search for certain conditions and keep adding all tasks that fit condition?
I use that now in another project but it was super tedious to set up because I wanted the checklist to be vertical which is most natural.
So I created fields on a canvas from top to bottom like you would want in a checklist that would then auto populate into regular table. I don’t want to go through that kind of set-up again.
Hmm I’m trying to find the simplest approach.
In the example below I just simply duplicated using a filter and then set that filter (checkbox) back to unchecked.
I think this could be quite straight forward, but I might get caught with a learning curve soon.
Is this along the lines of what you did?
What are you trying to do?
Chris DeAngelis
Partner & General Manager
Alliance Development Group | www.adgchina.co
+86.18601243272 +1.212.647.0076
This was just a demo example learning button use.
But I recently set up a budget tracker. I want to simplify forecasting for recurring transactions.
in Notion I had 1 button per transaction which means many clicks per month to generate forecasts.
Currently im thinking of: Button → filters last recurring → duplicates → modifies transaction date by adding the frequency interval.
Any better ideas for handling recurring?
Easiest is setting a button in a column and changing defaults when to disable it. Could be time, after some field, whatever. Then create a separate button on the Canvas that pushes the column button. It will push them all that are not disabled. Then you push this canvas button manually or through an Automation.
Chris DeAngelis
Partner & General Manager
Alliance Development Group | www.adgchina.co
+86.18601243272 +1.212.647.0076
Great, thanks. I hadn’t considered putting the button in the row for filtering.
Will make it much easier to maintain if each row owns the logic for push / no push.
