Report Builder
Saved SQL reports over the SQL Playground's shop data. A report's SQL declares its own question boxes ({{From|{last_week_start}|date}}) and its columns carry their formatting ("Total|$|sum"): money, dates, subtotals, links, tooltips. Sort, filter, copy as a table, download as Excel, or pull it into a script with a key.
Customers 2
| ☆ | Jobs for a customer | #7 | sample | |
| ☆ | Top customers (Pareto) | #6 | sample |
Jobs 3
| ☆ | Job: parts tabs | #2 | sample | |
| ☆ | Job: time log | #3 | sample | |
| ☆ | Late jobs | #1 | sample |
People 2
| ☆ | Hours by employee and day | #5 | sample | |
| ☆ | Time clock exceptions | #9 | sample |
Shop floor 2
| ☆ | Scrap cost by reason | #8 | sample | |
| ☆ | Station throughput by week | #4 | sample |
Where this came from
This is a port of the "Auto Table V2" report page I built for an internal ERP site at work: there it runs against SQL Server with Monaco as the editor and group-based security. Here it runs on Postgres through the SQL Playground's read-only sandbox role, uses CodeMirror, and anyone can run the public reports. The question grammar, column directives, subtotals, copy-as-table, the hand-written .xlsx writer (no library: it's a zip of XML), save history with line diffs, and key access all came across.