And if any of you are wondering what sort of a whacko developer would store JSON data in a field, here’s one reason.
Wow, I was browsing the support docs and saw this beta but no signup link. One of my scripts stores JSON data in a text field, so this is perfect.
THIS. IS. AMAZING!
Aw! I tried it, but I think missed the point of this @Kasra - I’d love to be able to build a JSON file from my Airtable Schema…(i.e. build a different JSON structure than the output from the API)
This is still cool, but I will normally just use VSCode for this - I’ll never have a need for something else to be honest.
Haha! Nope - I do it all the time, but I actually usually use formulas to build out my JSON at the record level, but what I’ve found at the moment, is I’m doing a lot of lookups in the apps I’m building, when it would be amazing just to be able to build a read-made JSON file with all of that done for me. If I could define a custom JSON schema from my Airtable that would be huge for me
Aw! I tried it, but I think missed the point of this @Kasra - I’d love to be able to build a JSON file from my Airtable Schema…(i.e. build a different JSON structure than the output from the API)
This is still cool, but I will normally just use VSCode for this - I’ll never have a need for something else to be honest.
Haha! Nope - I do it all the time, but I actually usually use formulas to build out my JSON at the record level, but what I’ve found at the moment, is I’m doing a lot of lookups in the apps I’m building, when it would be amazing just to be able to build a read-made JSON file with all of that done for me. If I could define a custom JSON schema from my Airtable that would be huge for me
This is possible - I have one project where we used GraphQL to create an entirely different interface into the Airtable API.
Indeed, the VS Code editor is tough to beat, but we have to consider all those users who will never use VS Code and who may need to view JSON data in a structured manner. I see this new capability as a “green light” to utilize JSON payloads as data objects without fully driving our client/users off the cliff. Until now, embedding JSON in a text field was a rogue idea despite the advantages it presents in many use cases.
That’s exactly what GraphQL does.
Wow, I was browsing the support docs and saw this beta but no signup link. One of my scripts stores JSON data in a text field, so this is perfect.
It’s automatic I think - you click it and it registers based on your Airtable account.
It’s automatic I think - you click it and it registers based on your Airtable account.
Yes, I got it now. I was referring to when I first noticed the JSON beta in the support docs a couple of days ago. There was no link in the support doc back then. Another support doc said that publicly available betas would have signup links in the support doc page. Airtable sure has a lot of different ways of handling betas!
Yes, I got it now. I was referring to when I first noticed the JSON beta in the support docs a couple of days ago. There was no link in the support doc back then. Another support doc said that publicly available betas would have signup links in the support doc page. Airtable sure has a lot of different ways of handling betas!
LOL - yes. This is the subtle cost of doing things more elegant, which can sometimes be another way to describe “obscure”.
Yes, I got it now. I was referring to when I first noticed the JSON beta in the support docs a couple of days ago. There was no link in the support doc back then. Another support doc said that publicly available betas would have signup links in the support doc page. Airtable sure has a lot of different ways of handling betas!
Relevant: https://community.airtable.com/t/request-centralized-location-for-beta-listings/30253
Whoops, it’s in a locked category. Well basically the idea of having a centralized Beta announcement/sign-up page has been suggested, namely that every open beta be announced in the Announcement category, probably with a tag of “beta release” or something similar.
