Archived from the Bravo community forum (2021–2026). Some answers may refer to older versions of Bravo.
many people have been having a similar issue. As a previous person has said:
“I'm running into an error when trying to setup a patch request so users can update their profile information (using Airtable API). The JSON Code tested as valid and the PATCH request works fine when trying within Bravo Studio. Patch request is bound to input destinations.
However when opening bravo vision and submitting the changes the request doesn't go through (hence no changes in my Airtable sheet). Any ideas on how to solve this issue?”
I have the same issue, on bravo vision it says error 422. I went into debugging/troubleshooting and it seems the record id isn’t being sent to the airtable and hence it makes it so airtable doesnt know which record its supposed to patch/delete. Here is the debug event with important part underlined:
“{
"appId": "01JJX5X9YKSQVWS25DFD7VXQGZ",
"nodeId": "01JP790V9HQ42YHQAT6Z453RE9",
"timestamp": 1741876184679,
"source": "apps-service",
"type": "error",
"code": "failedRequest",
"context": {
"resourceId": "01JJYG2G5TN080PMHAYDEJJ0ES",
"operationId": "01JP7WTK94B8HMPGWHWFJW8TBG",
"request": {
"url": "https://api.airtable.com/v0/appcUX2XnACYmy5ZR/Intro%20Data%20for%20POP%2F",
"method": "PATCH",
"headers": {
"user-agent": "Bravo Data/1.0 (app:01JJX5X9YKSQVWS25DFD7VXQGZ)",
"x-forwarded-for": "118.200.157.48",
"Authorization": "Bearer patqu7NjN59aLcJB2.7e26489a680b29c7fb3daaf075f1aa5bb334d791ab4a5f4bd4b04207525317a3"
},
"body": "{\"records\":[{\"id\":\"\",\"fields\":{\"PODate\":\"2025-03-13\",\"ORDate\":\"2025-03-13\",\"PD\":\"8th\",\"Deviceid\":\"5745B42E-6C85-4FFD-9130-3F38475C9130\"}}]}"
},
"response": {
"statusCode": 422,
"headers": {
"date": "Thu, 13 Mar 2025 14:29:44 GMT",
"content-type": "application/json; charset=utf-8",
"content-length": "172",
"connection": "keep-alive",
"set-cookie": "AWSALBTG=afyFFLt9LAbaHJ09wHVWFoGlm/6tezAV5JrY01faKGSbWmbXXzqGz0ImW9tDsrK0DVBA7wJJDTWw20vj7L72oa4MR2EqrCYJt0hCOKb3+YS4tayBovURupgGWMJMDUwAofuhV2CYpA+X85jUrdOfpGWZLt2serLfHiaQViQyvwFUydBsd90=; Expires=Thu, 20 Mar 2025 14:29:44 GMT; Path=/, AWSALBTGCORS=afyFFLt9LAbaHJ09wHVWFoGlm/6tezAV5JrY01faKGSbWmbXXzqGz0ImW9tDsrK0DVBA7wJJDTWw20vj7L72oa4MR2EqrCYJt0hCOKb3+YS4tayBovURupgGWMJMDUwAofuhV2CYpA+X85jUrdOfpGWZLt2serLfHiaQViQyvwFUydBsd90=; Expires=Thu, 20 Mar 2025 14:29:44 GMT; Path=/; SameSite=None; Secure, brw=brwNf2evRCSAOqCS1; path=/; expires=Fri, 13 Mar 2026 14:29:44 GMT; domain=.airtable.com; samesite=none; secure, brwConsent=opt-out; path=/; expires=Thu, 13 Mar 2025 14:34:44 GMT; domain=.airtable.com; samesite=none; secure",
"server": "Tengine",
"strict-transport-security": "max-age=31536000; includeSubDomains; preload",
"access-control-allow-origin": "*",
"access-control-allow-methods": "DELETE,GET,OPTIONS,PATCH,POST,PUT",
"access-control-allow-headers": "authorization,content-length,content-type,user-agent,x-airtable-application-id,x-airtable-user-agent,x-api-version,x-requested-with",
"x-frame-options": "DENY",
"x-content-type-options": "nosniff",
"etag": "W/\"ac-K0K+LDv1fehqy1WWNqkbVDOqnxo\"",
"airtable-datacenter-regions": "us-east-1",
"vary": "Accept-Encoding"
},
"body": "{\"error\":{\"type\":\"INVALID_RECORDS\",\"message\":\"You must provide an array of up to 10 record objects, each with an \\\"id\\\" ID field and a \\\"fields\\\" object for cell values.\"}}"
},
"time": {
"dns-resolve": 1.033651,
"request-error": 390.158991,
"$$total": 391.192642
},
"error": "Request failed with status code 422"
},
"id": "1741876184679-apps-service-failedRequest"
}”
PLEASE HELP
1 reply
Hi @jonas w is user_id the id you’re saying is not being sent?
right away I would suspect the id variable is not being passed along from the user information
e.g. I imagine you have a form that lets the user change the info, and you’re either showing the user info in that same form or in the previous screen (before the user hits edit) I guess;
my guess is any of these 2 UIs is holding the user id that you need to pass along but the variable is being named in a different way than the id variable you’re using in your PATCH
could you share screenshots of the following:
- selected data in the user info endpoint in your API in Bravo
- JSON in the PATCH endpoint that edits the information (the one it’s now working) in your API in Bravo
Wrote something in this thread and want it removed? Request removal
Ask the community on Discord
This archive is read-only. New questions, office hours and product updates now happen in the Bravo Discord.
Join the Discord