Hey Gliders!
I’m building an app in Glide and need some help with triggering the creation of a new row (and Row ID) and ensuring the app starts writing to it correctly when a new user journey begins.
My app is based on three tables:
- Hexagrams (H): Contains titles, descriptions, and images.
- Readings (R): Holds most of the app’s logic and outcomes from the logic.
- DisplayHexagrams (DH): Pulls results from Readings and matches them with the appropriate content from Hexagrams as well as storing user generated question and notes.
Here’s the user flow:
- The user goes through four screens (Home, Cast Hexagram, Readings, Journal) where they enter a question and then reflect on their reading in the notes section.
- Once the journey concludes, the app returns to the home screen.
Currently, I have a new row created in the Readings table with a unique Row ID each time. However, when a user starts a new session/new question, the data is still being written to the previous row instead of the newly created one.
I’d really appreciate any guidance on how to ensure Glide begins writing to a new row for each new session. This is the last major hurdle before I can publish the app after four months of development.
Thanks so much in advance!
How are you creating this row?
I would say that in the last action before the journey concludes, you add a new row, and filter your flow to build on that row.
However, I might have more questions. Is this like a custom form? Why do you need to pre-add a row, and not treating it like a form, only submit after everything has concluded?
1 Like
Thank you so much for responding . Really appreciate your help.
I create this row by using an action in my final workflow (‘Complete Reading’). This is the ‘Readings - add a row’ action detailed below.
This then adds a row to my Readings table detailed below Processing: image.png…
The app is designed to act a little like a horoscope. You ask a question, it delivers a reading from 64 descriptions and associated artwork, the app records your initial question and answer for that unique reading and stores the unique reading, artwork, question and answer to return to at a later date. You can reflect on that reading using the journal functionality (notes).
I’ve managed to build something that completes a single rotation through this journey but cannot replicate it. My understanding is that you would need a new row ID for each new question, reading and notes for each user. I would like the user to be able to look back at these questions, readings and notes which is why I felt a new Row ID would be required for each new interaction. Appreciate your help!
1 Like
Based on the flow above, isn’t it easier for a user to click a button to add a row themselves when they want to ask a question?
Then the flow continues inside the details view of the row they added, does it work like that?
