Great question @chris_homburger - the short answer is while the history exists as you’ve observed in Row Detail, it’s not currently accessible via the formula language. We actually recently explored exposing this with a set of of formulas like historicalvalues() and asof() which let you pull point-in-time information on a specific object (like rows in a Table). Curious what type of report you’d like to build with this info - is it number of updates to a specific record, or something else?
One other solution is similar to what you’ve implemented already in your doc - which is tracking Clients and Actions in separate tables, with the Actions table incrementing with every action taken by your team. Using that Table, you could build out some metrics / visuals showing progress over time. Would that help here, or are you looking for something more granular?
It would be a way of doing it, but we’ve been using the table without this and already have one parent/child table relationship in the document. Doing that would be a little wraparound and add more overhead to the document, which we’re looking to avoid.
Specifically, we have three health ratings, and would like to be able to see both the count/% of each over time (as a line chart) and the adjustments that were made each week (how many moved up and how many moved down). Some combination of historicalvalues() and asof() would be great—especially if asof() could be bucketed into time.
So it’s two measurements:
How many fields were altered in a date range, and in what “direction” (e.g. between 1/1 and 1/31, 10 improved and 5 degraded). That second step is the kicker, I know, but we’d just need a way to map a numerical key to the colors (e.g. green=3, yellow=2, red=1) and do sum(newState - oldState) to get a meaningful metric.
How many fields were in state A/B/C at a specific datetime (this would be Table.filter(health=green).asof(Date).count(), or similar)
The report built out of this would give us a sense of how our projects are tracking historically throughout a period of time to see if process changes we make have an impact on their health.
I can’t really speak in name of Coda, but to my opinion the “unlimited version history” is more made to roll back to a previous version of a doc. According my logic, it has no meaning to roll back more then several months.
Looks in my opinion the better way to safe your history records and from a perspective of doc size, you might also consider to export this data.
Personally I am very happy moving reference docs that are not active to be clean up.