A series of small usefull changes

Question

I have noted several small but recurring limitations and ideas related to Airtable. I would like to understand whether these are on the product roadmap and, if not, whether practical workarounds exist.

Enforcing a true unique key constraint on a table’s primary field
Right-aligning numeric and currency values in the list interface
Rolling up values in a self-linked table currently requires separate rollup fields per level and an additional formula to consolidate them into a single field
Gantt chart dependencies only support day-level granularity; hour-level dependencies are needed
A native delete-trigger mechanism

Could you advise whether any of these are planned for future implementation, and what recommended workarounds exist today?

vera_green · Answer

I can speak to a few of these. I have seen Airtable’s published roadmap but I can’t seem to find it now. But here are why some of these may not be in consideration:

1 - Tables do use a unique key, which is not the same as the primary field. It is hidden by default, but creating a formula field with “record_id()” will reveal it. All external applications use this as the true record key and you can use it too.

5 - Though not available in the standard automation blocks, this is easily done with a scripting automation step.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded