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.