Thanks for the warm welcome, Piet. Not sure what additional information you are looking for.
Please let me know.
Our current system allows each dev to add their daily update into $dailyUpdate table.
dev selects the $project.name into a column (connected to $project table) and provides the update.
We want to transport the updates into each $project . not sure what coda data structure is appropriate for the same.
This keeps the number of rows to a minimum, while you still have access to the history. And if the devs update in this table, maybe using a view, then there is no need to copy from one table to the next. Just before each update, they need to click the button. That will move the current comment to the archive column, and allow them to capture a fresh comment. (Just thought now, when cleaning out the current comment column, one can get Coda to put todays date… A Coda doc is never complete. )
I generally prefer to have as few table as possible. (If you’re an IT person - 3rd Normal form no longer applies.)
Hi @Amit_Handa!
I think I’m following what you’re trying to do. Instead of trying to add the updates as “comments”, I would use a subtable. Essentially make a column on your project table that looks up all updates for that project → $dailyUpdate.Filter(project = thisrow)
And then you can surface those updates as a subtable (when you pop out a row), or even as a bulleted list, etc.
Thank you so much @Max_McEwan@Piet_Strydom , made my day.
In the end, subtable worked fab for my usecase. Yet to learn how to show them as a bulleted list (or custom format them more).
But for now, it suffices.
TYVM !!! have a great day.