Actually, it would be great if you could check my backend.
Using only the solution proposed by @dilon_perera on the other topic is not enough, because sometime I need the Custom Action.
Right now I’m creating Airtable records using the Create action of Adalo, and it works.
When I have to update an existing Airtable record sometime I can use the Update action of Adalo (when the newly created Airtable Record is among the available data in the screen), but sometimes I can’t. In this second occasion, I necessarily need the Custom Action to update the Airtable record.
I created a new property to the Adalo Users collection called “Airtable ID”, and when users signup the Airtable IDs are successfully stored there.
Then, when I try to update the Airtable record with a custom action "setting id = “Logged in user’s Airtable ID”, nothing happens.
Yes, Update Airtable with Adalo “Native” action, only if you are in a “Current Airtable Record” because adalo needs to connect to api and collect data.
For the custom action also correct you can use anywhere as long as you use custom action with record ID.
I just tested from my side.
The record is not created.
If I use the “native” Adalo “Create Record in an External Collection” the record is created, but then when I try to update it with the aforementioned Custom Action, it isn’t updated.
Hi, I would need to check your airtable table and the custom action. Are all Airtable fields with similar structure as Adalo JSON Request? E.g. Number, text fields and so on.
I think I found the problem: both in the Create and Update action, if I leave one field empty, the action doesn’t work.
I tried filling every available field (even putting “false” in boolean fields), and both actions work.
Hi @Productology ,
In the Patch I would expect that (A PUT Would just put all blank) if API follows standards.
For the create action, this is odd, because if you don’t have a mandatory field, this by default, should not happen and just ignore the empty value.
