Have you ever wanted quicker, easier, and more structured insight into your doc / table structures?
Can I see a quick hand for those out there who have large tables, large enough that you have forgotten which columns are really important or vital to your docs structure?
Or maybe you want to keep better notes and documentation for a crucial document to help new users learn about the table structures, columns, and column purposes?
WELCOME THE AUDIT PACK:
Its still in construction, but allows you to pull your table and doc meta-data into tables themselves! The tables don’t even have to be in the same document!
You cannot edit the actual columns formulas, types, etc from the table no.
Right now the use case I have in mind is more thorough documentation on a tables columns. You can of course add columns to this table like the “notes” canvas type column you see at the end to then document, add info.
Would love to know if you or others have any other use cases that come to mind for a pack like this though!
I have created a doc that essentially runs my entire small business operations. My business is a copy and paste model for 100’s like it. I have thought about one day setting up my doc for others for some sort of fee and something like this would be certainly help make a fairly complex doc understandable for others.
Also for me, when I go back to a formula I created months ago and can’t make heads or tails of lol.
Might be interesting to see if you could create a version history of sorts. Even if it was just the last iteration. I have a number of users in my docs and locking can sometimes be prohibitive. When docs are unlocked curiosity tends to get the better of some and formulas get jacked up. Coda’s default versioning is a life saver but formula changes are near impossible to track down other than a guess and check method… Just thinking out loud (silently via keyboard).
It would be great to see a column type for each column.
Are you planning to also list out a table of Tables? If so, it would be useful to show (on your “Column Data” example above) if the formula is referencing another table (and what that table is).
Ya this is great. I have a large doc that runs a few different processes. The doc is years old and you better believe I’ve got all kinds of extraneous columns left over from past ideas and experiments. Would love to see everything in one place.
Also being able to scan for outdated formula approaches that I now know better solutions for.
What a great idea. I would also find it really useful to run a report showing all references in a doc to a particular table, column, row or formula. When planning changes to a complex doc, it’s not always easy to refresh one’s memory on all the different ways that a particular object is used throughout the doc, which sometimes leads to changes having unintended consequences and needing to be rolled back and redesigned. The Doc Map goes some way towards this, but not quite at the level of granularity needed.
I can enter any table in the database, and get this info.
It looks very similar to the screen shot in your first post, but I couldn’t figure out the table to which the columns refer? Is your info per table, or per doc?
And if @Leandro_Zubrezki and you could show the links between tables that would be amazing.
(2) Find your docID
There are multiple ways to do this, but the easiest way is with Codas Doc Id Extractor found at this link: → Coda API (v1) Reference Documentation
It can always be found in your URL too. Its the string that is after the page name and the lower case d up until the /
So if this was my url: https://coda.io/d/Jedi-School-Signups_dPLcnImR-ON/Example-Table_sunUR#_luUzF
My Doc ID would be: PLcnImR-ON
(3) Find your table ID
This you can do easily in your doc by selecting the little snowman menu next to a table and copying its id
for those out there who have large tables, large enough that you have forgotten which columns are really important or vital to your docs structure?
I would also find it really useful to run a report showing all references in a doc to a particular table, column, row or formula. When planning changes to a complex doc, it’s not always easy to refresh one’s memory on all the different ways that a particular object is used throughout the doc, which sometimes leads to changes having unintended consequences and needing to be rolled back and redesigned. The Doc Map goes some way towards this, but not quite at the level of granularity needed.
Hey there!
