Hi, you may know me as KAM, the guy who’s been cranking out some pretty pleasing-to-look-at dashboards around here. These are five small, additional options that I believe would add a lot of ROI relative to the effort needed to build them.
TL;DR
- Let tables show newest entries on top, natively.
- Let Choice Lists be defined once and reused across columns.
- Give internal one-off data entry the same polish as public Forms.
- Let Automations trigger on a date/schedule, not just on data changes.
- Wrap long column headers instead of truncating them.
1. Native newest-on-top row order
Right now, showing recent entries first means adding a manual sort to every single view of a table, since it’s not a property of the table itself. For logs like orders, updates, or tickets, “most recent first” is the natural way people expect to read the data, not a special case.
The fix: A row-order setting on the table (default globally or toggle per table, either is fine) so every new view is newest-first automatically, and new rows are added at the top to match.
Payoff: No more re-sorting every new view, and no more mismatch between how a table is sorted and where new rows actually land.
2. Reusable Choice Lists, without needing a Reference table
Choice and Choice List options live on the column, so the same list (Status, Priority, Region) gets retyped on every column that needs it, and a single update means updating it everywhere it’s duplicated. Reference Lists solve a similar problem, but only by pointing at a full table, which is overkill for a simple, fixed dropdown.
The fix: Let a Choice List’s options be defined once, internally, as a named reusable set, and attached to as many columns as needed.
Payoff: One edit updates every column that uses it, instead of hunting down and fixing each copy by hand.
3. Internal/External toggle on Forms
Form mode already has the polished, guided layout that makes data entry clean and low-error, but it’s built assuming external/public submission (shareable link, standalone page). For an internal one-off request, that’s more setup and more public-facing surface than needed. There’s no way to keep the same Form experience but scope it to teammates who already have document access.
The fix: Add a simple Internal/External toggle to Forms. External keeps today’s behavior (public link, standalone page). Internal restricts the form to users with document access and skips the public-link setup.
Payoff: Reuses the entire existing Form UI as-is, no new styling engine or view type needed, just a scope toggle, so it’s likely one of the cheapest items on this list to build.
4. Schedule-based triggers for Automations
Automations already send emails natively when a record changes, which is great. But there’s no way to trigger on a date or time by itself, like a due date arriving or a renewal coming up. That still requires an external scheduler like n8n or Zapier.
The fix: Add a schedule-based trigger type to Automations: a recurring schedule (daily/weekly digest) or a date-field trigger (fire when today matches or passes a date in a column).
Payoff: The email infrastructure already exists in Automations, so this just adds a trigger type, and removes the last reason to reach for a third-party tool for due-date and renewal reminders.
5. Wrap column headers instead of truncating them
A long column header either forces the column to stay wide just to show the label, or gets cut off with “…” once you narrow it. There’s no way to see the full name without widening the column.
The fix: An option to wrap header text onto a second line instead of truncating it.
Payoff: Small, low-risk, and immediately noticeable for anyone working in a wide, dense table.
