We are wondering if we have hit a complexity point in Adalo, since we are stumped in how to achieve what might best be described as “cascading databases set-up”.
Here’s our objective - we are trying to create an app that collects data from people in the context of their experience participating in an event. We have a set of stock “questions” for which we want to collect answers. But obviously, we need to collect answers within the context of one event.
So - what we need is to be able to create a new event in the database, and have that creation trigger the creation of empty tables in the database to collect answers to our questions for that event. The questions are standard across all events…
Right now, we’ve gotten as far as creating a new answer table for one question, but you have to use that question’s activity to create the next question’s database. We don’t want that - we need spontaneity, the ability for an event admin to say “OK, so now go to question 3 and answer the question”, followed by “OK, so now go to question 8 and answer the question”.
Anyone have thoughts on how I can simply trigger what might essentially trigger the creation of all the database tables I need to hold answers to all of the questions in a single or very few efforts in an app?