This is sweet! Thank you.
I think that something this could benefit from is a Private account feature.
Right now I’m thinking of using it on a doc that I manage for a client, but I have to generate an API token for it which will only have access to that particular doc.
This isn’t ideal because I’d prefer to be the only one that can use the Pack, if someone else wants to use the Pack they’ll have to sign in with their own API token.
This way I don’t have to think about the possibility that I might forget to generate an API token that applies to only that particular doc. Otherwise, any user of a doc with this pack installed could potentially Audit ALL of my docs, haha. I might not want that.
Ooh, one more thing!
It’s always nice to provide the formula for getting the current doc id in a field hint:
RegexReplace(thisDocument.ObjectLink(), ".*/d/_d", "")
Edit I see you did, but it’s actually quite the bummer that the argument hint can’t be copied.
Maybe you could do the Regex on the Pack side so that
thisDocument could be passed directly?
Good thought Connor! Ill look into it
Hi, first of all thank you for you work! This is really helpful!
I’ve started using it and found a limit of only one Column Data table Not sure why there is a limit…
Also, would be great to have an option to provide multiple table IDs in the future.
Do you think that the Column Data table limit could be unlocked or there is a technical problem? Thank you!
Hey @Farid_Sabitov !
So glad you are liking the pack. Can you give more context as to your issue?
You are trying to have two separate column data tables in a doc and it won’t let you? What error message does it give you!?
Screenshots always welcome!
Thank you a for a quick reply! Yes, here is the screenshot
As you can see there is a limit of using only one table per document and it’s not allowing adding extra “ColumnData” tables
All the best,
Got it - totally clears it’s up. I’ll look into it and get back to you.
Hey @Farid_Sabitov (and anyone else reading this thread) -
I’ve got us a workaround for now. The limit of a single sync table is something on the Coda Pack side (nothing that I wrote in the code and nothing that I can actually change)
But you do have the option to “Add Another Sync” to an already existing table. To do that:
- Head to table options
- Select “Add another sync”
Then updated the Audit pack code to include a “Table Id” column (as seen in the screenshot below). You can use this new column to then make as many filtered views of your master sync table as needed or group by that column. (if you filter by this Table ID column, you would get a view showing a single table)
Hi Scott, fantastic pack thank you !
Not sure if this is a Coda limitation or a bug, but I have a rather large doc with more than 100 tables+views and it seems I can’t sync more than 100 rows even if I select a table limit of (overkill) 10000 rows. Is this known behavior ?
I’ll put a continuation on the pack to sync larger amounts. What table of the Audit pack are you using specifically?
Hey Scott !
This is using DocTables table.
Got it! I expect to push a fix for it by early next week
How many is it currently syncing?
56 tables + 44 views.
I pushed a fix! Can you re-sync your table and let me know how much you load?
I just successfully loaded 605 rows on a DocTables sync table
99 tables + 160 views synced
Time to do some spring cleaning !
Thanks a lot for the quick fix !
Two new additions to the Audit Pack
(1) New Parameters for easier entry
DocId parameter that was required in every table can now simply just be the copy/pasted docs URL from your web browser
Hoping this makes it easier for newbies and seasoned users alike
(2) New Sync Table
I heard from many of you that you want to sync in the ColumnData on more than a single table at a time. Currently you can do this on the
ColumnData sync table, but you have to manually add another sync each and every time for every table you want.
If you have a small doc, that is ok - but not for huge docs.
Now, with the new AllColumnData table you can sync in the column data for every table in a doc automatically!
i have been using these packs with a client with dozens of docs, hundreds of tables which have many trends of formulas, non of whice i was involved in.
so this extension to the pack is just what i need
this saves me many hours popping in and out of the formula editor to try to understand everything.
well done sir !
Alright! One more big update
Situation: You have a LARGE document with many tables and performance is starting to drag. Identifying the tables with huge row counts is crucial
Solution: The new
I added a
rowCount() formula that can be inputted into a column in the “Doc Tables” sync table. It reads the TableID from the relevant row and returns how many rows are in that table.
You can then easily sort your “Doc Tables” off the RowCount column and VOILA! You now have identified your most problematic tables and can attack them in a systematic way
@Scott_Collier-Weir, you are a machine
putting out packs and solutions at a great rate
these recent changes to the audit packs are great
making them so much more useful
well done indeed
It is thanks to people like you that Coda will become excellent for many situations.
I hope one day to be able to do what you did and learn how to develop solutions to help the community.