I’m also interested in this
As old as this request is, you’d think they would have added schema access to the API by now, but they haven’t.
I came up with a kludge to do this. If you can take a sizable swath of data and perform a fast aggregation on option list fields, you can determine all the possible unique values, ergo - the option list array.
Completely bad approach, a workaround with a capital W, and likely to add some latency to your front end UI.
Airtable MUST address this now to regain its API composure.
As old as this request is, you’d think they would have added schema access to the API by now, but they haven’t.
I came up with a kludge to do this. If you can take a sizable swath of data and perform a fast aggregation on option list fields, you can determine all the possible unique values, ergo - the option list array.
Completely bad approach, a workaround with a capital W, and likely to add some latency to your front end UI.
Airtable MUST address this now to regain its API composure.
I agree completely. Hard to build self maintaining forms without this. Leads to data integrity issues (when using the typecast parameter for instance).
So if I understand correctly, it has never been added since 2016 ? It’s even doable in Scripting Apps so why not on the api ?
I guess we should start implementing our own little database on the side to stock all those things, because looping through all of my records for all of my select and multi-select fields value is definitely not an option.