I have a form that is hooked up to airtable db.
Logs are showing an error on the first form field where someone enters their name.
In the payload, things don’t look as I’d expect.
The hierarchy looks weird. Why is everything under name: (2 levels, even!)
And also why is name: in there 3x?
I’m spinning in circles
I’m not sure if this is root cause and I’m not expert in payloads, etc, but this seems likely why my form is failing with a 422 status code
The name field is text and it’s supposed to write to a “short text” field in Airtable.
I tried to throw in all possible relevant images but the system is not allowing it. Frustrating. But hopefully the one I picked is explanatory but wish I could share the config for the different parts.
UPDATE
I put one input form into a page with a submit button and created a new airtable table.
It still won’t write.
Airtable API has explicit write permissions.
At times I’ve seen no error in dev tools but it still doesn’t write.
Is there a good form tutorial out there? I don’t see much on youtube.
It just doesn’t seem like a low/no code platform should be this hard. I’ve had other tools write to Airtable and it was trivial :-/
Hi Klickpath, welcome to the community 
I think this might be an issue on how you are passing (structuring) the data to your Airtable.
I’d love to see more information about this, can you share a couple pictures on how your forms are set up in WeWeb? (You couldn’t upload several pictures before because you have a brand new account in the community, but you can try now)
I would like to see the formula or array that you are passing on you form inputs.
Thanks. I actually tried to bail to Xano but am encountering what seems to be the identical issue.
I will add some attachments but the things I"m not sure of:
- most of the docs seem to be for dynamic pages (GET) and I’m having a hard time finding a solid tutorial for POST operations.
I’m not clear on the Collections and have tried to map in a few ways, at times, my mapping seems to disappear.
I also could not get a “On submit” and only could get “On execute” and that seemed to be a scope problem that I’ve now hopefully fixed.
Things I know:
Submit button is a submit button type
Workflow is now connected to the Form container (I thought it was before, but i think it was global)
Collection was fetching automatically but since this is POST, I disabled that (hopefully the right thing to do)
Things I am not sure about:
I seem to be able to do data binding from the Data
Collection seems like a thing for FETCH and GET but I’ve tried to set it up anyway.
One issue I see, the base name changed and where i put a rectangle around it is correct and where I circled it, in config, is correct
If there are other areas you need screenshots please let me know.
Thank you so much
One part that I believe could be wrong is in how you are mapping the submit
Can you share that screenshot?
Also, I believe watching this mini course could help you:
https://academy.weweb.io/build-with-airtable/display-data/
I oon’t see anything about Submit in the screenshot (or am not understanding something). Looks like you’re on the Record ID. I did not map that and assumed it would be auto generated, but am not really understanding your screenshot in light of Submit.
I also don’t think I have any equivalent of “Selected line”?
I had gone through that course, but it is about getting data from Airtable for dynamic pages. I can’t find anything about POST type operations. Am I missing something in there?
It feels like there is so much documentation on Get/Fetch to create dynamic pages. Property sales, the tutorial you reference.
But I"m not finding anything much on writing to a db and anything I’ve seen was probably with Xano on the backend.
I’m hoping the screenshots cast some light.
My screenshot was just an example to show you what it is that I wanted to see: the dynamic data that you are passing to each input.
I want to see what you are passing to “Name“, “Email“ , “what business“ etc (show me your formula)
I think you have a mistake in one of those. I think you are passing down the entire array instead of only the value you want.
I bailed and went to Xano. I figured that if Airtable was supposed to be easy and it wasn’t going smoothly, I may as well wrestle with the more difficult one.
I now have my weWeb form writing to Xano.
The problems were:
I did not understand how to get a POST method
Had a scope issue in that my workflow was global rather than on the form (I still may not be fully understanding this as I’m not sure why you’d have global workflow).
And I had type issues from selecting the entire Object rather than the property I needed.
I probably could make Airtable work at this point, but Xano is going to support more of what i want to do.
If it’s better to delete this thread, let me know.
Thanks
1 Like
