Archived from the Bravo community forum (2021–2026). Some answers may refer to older versions of Bravo.
Hello All,
We are getting close to finishing our app, and we ran into another slight issue. We currently heavily rely on POST API requests to bring data from the app to our database in Xano. In a previous version of the app we had all information asked on a single onboarding page, but now for a smoother experience we have given each question its own page.
However, this seems to have created an issue where because each page is a separate action and API call, it cant create a singular database entry. Before the single page was easily populating our database, but now we can't even get one question to populate.
Any tips on how to handle this or perhaps advice on us maybe misinterpreting the issue here?
3 replies
Hi,
what you describe is a result of Bravo not allowing any temporary storage. The only way I could think of would be saving the users entry into a third party storage before posting to Xano in the end. You could even do this in Xano by creating a table for temporary use. It would store all inputs with an identifier of the user. Then, when the last input is filled, gather everything with that identifier and post it into one record in your actual DB.
I haven't tried it but I hope the concept already helps you :)
Thank you for the reply! You've been our main source of tutorials on Youtube, you're fantastic! Unfortunate its not supported but we will try you're concept and see if it works. Thank you so much!
Happy to hear that, good luck :)
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