The third release of the dynamic CRUD app, and the point at which it stops being a data-entry form and becomes a dashboard. Charts, dependent dropdowns, coloured status badges and email alerts all come from the same spreadsheet configuration — not one line of code changes to get any of them.
Charts you declare in a cell
Write pie chart, bar chart or line chart against a field in the form sheet and that field gets that chart on the dashboard. A category field becomes a pie of the category split; a date field becomes a line over time. Ask for two chart types on one field and you get both. For someone who needs a dashboard and cannot write charting code, this is the whole feature.
Dropdowns that depend on each other
A field can name another field as its parent, with the child's values listed per parent value. Choose Sales and only the sales subcategories appear; choose HR and the list changes. Both sets live in the form sheet.
Permissions down to the column
Version two granted edit and delete per user. This one goes further: an admin can name specific fields a given user may not edit. The field still appears when they add a record, but it is locked when they open one to edit — so a clerk can set a request date at entry and never revise it afterwards. Users are created from a Manage Users screen in the dashboard rather than by editing the sheet.
Alerts and badges
Creating or updating a record sends an email — to the user's own address and to any email captured on the form itself. And a Buttons sheet maps status words to colours, so paid, unpaid and pending render as green, amber and red badges everywhere they appear in the table.
Everything carried forward
The admin still loads any form sheet against any database sheet, users stay locked to their own pair, fields are still rows with types for text, number, date, dropdown and file, and the filter keyword still produces dropdown and date range filters. Column visibility is new, and passwords are still changed in-app.
@rajtalk3766
via YouTube
