@John_Beaudoin_Jack wanted to chime in here as you appear to talking about yet another example of a “Source of Truth” solution in Coda, but ultimately one that failed and had to rely on an integration or maybe more accurately, a workaround.
I am trying something similar with a few tables, but I do have a few “mega” tables that are problematic. My issue is that logically what I tend to hear from Coda support and other users is that much of this should reside in discreet tables, but I need to relate a lot of the data, and the more tables I have, the more lookups I need, and that really gets cumbersome in a hurry. This is one of the reasons for a big request of mine:
and a few others that are similar.
And since I think this is a good thread on this issue, and @BenLee you are in here, too, I’d like to add once more that from my point of view, I’d like to see Coda Product Team move towards allowing much of this to be accomplished within Coda itself. To relate to John’s solution, I think it would be easy within one Coda Doc, or Coda “Instance” powered by more advanced Cross-Doc, to have both simple “todo” type tasks as a table, and projects as another table type, and relate them. I don’t think Coda is far from being able to do this right now, and I’d love to see you guys think about further improvements that would continue to allow either 1) ability to build out a full-featured solution via one Doc, or 2) Cross-Doc evolution that would allow a full-featured solution with may docs.
Thanks!