Hello Bubble community,
I have a problem with my Bubble Airtable plugin.
My workflow is simple, i click on a button, it creates a new record on an invoice table, i take two informations to create the record, the company name (no problem) and the items from an other table called item, there is no error in the workflow, but when i click on the button, a bug message appears. i tested my workflow and it’s the part where bubble grabs item list that’s causing the problem. I specified that the “item” section was a link to item table and a list.
Can you guy’s help me ? 
Same problem, I can’t write anything from Bubble to Airtable anymore… Very annoying.
I submit a bug report !
1 Like
Sorry to write this but the Airtable integration is not reliable. I’ve sent 4 bug reports two weeks ago about the airtable plugin, demonstrating some bugs on my side. I get great responses from the support (thanks @ Andrew Vernon !). One may interest other bubblers :
Once recommendation would be to make sure as you’re making changes in Airtable, that you’re reinitializing your fields to make sure they’re all set correctly on Bubble’s end.
One of the things that’s difficult about working with Airtable bugs is that they rely so heavily on how things are set up in an Airtable account we’re unable to look at. If the above suggestions don’t get you up and running again, please consider describing more about your base… How the lookup is referencing the data, where it’s coming from etc so that we can be better positioned to provide specific support on this.
So be sure you data is weel initialized ! About this, please @Bubble save the schema. For each initialization we have to set the type, the link record, etc. When you’re working with many columns, this is really time consumming and can generate new errors.
Also, please show us some exemple of values like for the API Connector, it would be easier for us to set the right type/format.
Hopefully Airtable will someday offer a swagger endpoint.
1 Like
About another bug reported with a demo, with a search constraint “is empty / is not empty” which did not work, here the answer I get two weeks ago :
I just gave this a try on our test Airtable account and was able to filter successfully using is & is not empty. But, I had to make sure that my settings were set up correctly and it didn’t work if the field I was trying to reference was a linked field. Instead, I had to set up a lookup field that pulled in the data I cared about from the other table and build my constraint on that field. The other thing you could try would be to build a view on Airtable’s side with the particular filtering you want and then reference the view’s records. It will essentially accomplish the same thing but Airtable will be handling the filtering for you. Might be worth looking into.
Here a new demo (I’m gonna send another bug report)
Not any error shows up in the editor. This is just a text (see airtable API doc) :
