Hey Mathew, thanks for getting in touch, and for sharing this thoughtful feedback.
100% agree and see the value in these ideas. Drawing on more of those programming concepts – tables-as-functions, for-loops, try-catch, global config values, etc. – would unlock a ton.
In the meantime, your approach to split up the workflow and separate concerns into multiple tables is the best way to approach it.
I know this is timely feedback, since I've seen recent conversations around revamping the workbook/table flow. We might edge closer into a more "component"-like approach. It may not solve the table-as-function concept, but may unlock easier visibility into the "lifespan of a record through many operations", so to speak.
Thanks again!
.png){kind=logo}
