12/14/2023 0 Comments Airtable api statusIf multiple records actually match, is there a way to tell which record will be updated? Or will there be an error? (Yes, I know that the three key field should uniquely identify a record, but sometimes bases have weird things going on.)ĭo all of the fieldsToMergeOn need to be included as fields in each record without a record ID? What if a field to merge on is supposed to be blank?įields to merge on cannot be computed and must be of the following field types: number, text, long text, single select, multiple select, and date. If a record ID is included, but that record ID does not exist, what happens? Will that throw an error? Will a matching record be looked for? If a matching record is not found, will a new record be created? If a record ID is included, does that mean that the record will always be updated, and a new record never created? ![]() Thanks for this new feature! It looks like a lot of work went into it. H "Authorization: Bearer YOUR_API_KEY" \ If you have any feedback about this feature, please submit via this form.Įxample request: curl -X PATCH / \ More details about this new feature can be found in the API documentation, under the Update records section. You can now add an upsert option performUpsert to the Update records API endpoint, so that if a matching record is not found, it will create the record instead. I’d like to set up some Airtable automations to send emails when a comment is added to an issue for example - but as there is no linked record / relation set in Airtable - I just can’t see how to do that.Hi everyone! We’re excited to announce one of our newest features - REST API Upserts. The only issue I have now, is making a relation somehow in Airtable. The solution for me (and again, I suspect this is written as best practice somewhere!) was to write the status to s simple text field (and have the choice component look up the options from a table in Glide) You can see this quite clearly in the videos on the links below. Doing this meant that there was a lag of a few seconds between updating the Status in the Glide App and it being written to Airtable, then another lag when it was sent back to Glide (I guess?) In Glide, my choice component was set to write to the linked field in Airtable. I’ve put below what the Issue seemed to be - and suspect it was bad practice on my part (but you live and learn),Īdding an entry was actually quick - things showed up in Glide instantly (and then sync’d over to Airtable as explained)īut I was grouping on a “Status” field - which was a Linked record field in Airtable (linking to a separate “Status Table” in Airtable). Thanks again for your help with this Jeff - think I got to the bottom of it! As long as you aren’t expecting something to happen within Airtable when that status is updated, then your app should work normally as it’s updated immediately in the app and synced immediately to the glide servers. It’s only communicating with the glide servers, and it’s the glide servers that communicate with airtable. ![]() ![]() The app has no idea whether or not Airtable is involved. It really shouldn’t affect app performance. ![]() It may take a bit to sync to airtable, but Glide still keeps a copy of the data on their server. I really don’t think it should affect performance in any way. If you create the status column in Airtable, then it will be non user specific in glide. There’s nothing stopping you from creating the column within Airtable though. To work around that limitation, Glide still allows you to create a column within the data editor, but the only option is to be user specific, which isn’t ideal since user specific columns hold unique values for each user. I think it’s an Airtable limitation where you can’t create basic columns in Airtable externally.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |