![]() While this is better for the visual experience, I wonder what are the recommendations regarding this naming convention when using the API. On most of the AirTable official examples, Tables and Fields have “humanized” names, usually starting with an Uppercase letter. This would allow to use an auto-increment PK field while displaying the label field in other tables. While using a comprehensive value as PK has great benefits in the understanding of the data, I wonder if that is possible to use a auto-generated field as PK and another more “user-friendly” field to be displayed instead of the PK. AirTable seem not to rely on such behaviour and usually use a comprehensive label field as PK. Primary fieldĬoming from the DB world, I’m used to having a primary key that is often a UUID or auto-incremented value. Since I’m planning on having a web app hitting AirTable API (data source), I’ll have to setup some caching mechanism very quickly. I could implement this, but if there is a trick/built-in it’d be awesome! The idea is to avoid the setup of my own caching mechanism (Redis, most likely) and rely on a predefined caching automated behaviour which would update the cache if there is a change in the data, and only from time to time. For instance, apply a default caching strategy when using API calls, and configure a cache invalidation/update when a row gets updated, every 30s at most, or something like that. I saw that the API rate limit is 5 request per second, I wonder if there are smart ways to configure a caching mechanism within AirTable. Is there any workaround besides customising the CSV fields order? (which would require some programming #boring) "state","name","label" Using the following CSV will therefore configure the state as primary field where I’d like the name to be the PK. Unfortunately, there is no way to select the primary field when importing a CSV as a new table. Selecting the primary field when importing I could also use another table to store the logo, but I don’t think that’s necessary because it’s a 1-1 relationship.Īnd I’d still have nested field with so it wouldn’t fix the issue either. Is it the recommended way to handle nested fields? This gets converted in CSV as follow, using the dot. Therefore, I’ll convert JSON to CSV and then import the CSV into AirTable.īut I wonder how I should convert those data to be efficient in AirTable and allow proper usage using JavaScript when fetching the records later on, through the API. Basically, AirTable may replace the backoffice I’m supposed to build.īut I have a few questions about how I should proceed, and I hope I can get some advices here! :slightly_smiling_face: JSON to AirTableĪirTable doesn’t support JSON format. Also, I saw there are tons of possibilities with AirTable and I’m also looking for creating forms and user interfaces eventually. The goal is to allow my teammates to see/update the data. I’m thinking about migrating an app, which is currently configured using a JSON format, to AirTable. I’m fairly new to AirTable and I’m trying to get a peak of all the possibility this tool has to offer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |