Archived from the Bravo community forum (2021–2026). Some answers may refer to older versions of Bravo.
We are launching our Alpha Version and wanted to make the login experience as simple as possible. Built-in variable ${device.id} will be used to filter data from Airtable instead of authenticating the users for sign-up.
Following the tutorial, at https://pcodina.medium.com/too-much-saas-on-my-plate-501710e61cf2, we met a 422 - Unprocessable Entity (value is not an array of record IDs) error while testing our API request:
JSON Body

HTTP Response

The main difference between our case and the tutorial is in the Airtable structure:
My case (tables Users and Objectives****)


Tutorial (table Subscriptions****)

P.S: I thought that maybe the solution is to refactor our Airtable.
4 replies
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