Whilst this is a really nice solution, unfortunately the issue I described here makes it unusable from a user experience perspective. So Iām afraid it looks like Iāll have to go back to the multiple screens/clickety-click option 
Iām sorry. What does it not do?
Functionally, I think it works fine.
But there seems to be some sort of race condition going on with the action sequence that ends up creating a very confusing user experience. Itās almost like the toggle is being flipped multiple times (it isnāt) and so the screen switches between the two states 2 or 3 times before finally settling down.
Iām not exactly sure what is going on, which is why I posted that other question. It could be because some actions are being fired before a previous action is completed, or maybe itās a data sync issue with several actions firing one after the other. But without knowing what the expected behaviour should be, thatās just wild speculation.
This is a fairly extreme example (with 70+ components on the screen, all being toggled on/off rapidly), but Iāve also observed similar behaviour with just a handful of components.
Make the toggle invisible during the event.
You mean set component visibility according to the state of the toggle, yes?
Thatās precisely what Iām doing.
I know these arenāt ideal solutions but until we have real fixes ā¦Iām just trying to help you get to that point
yep, I understand.
And I think that your solution is fine.
The problem isnāt with your solution, the problem appears to be that Glide is misbehaving and refusing to do what Iām asking/expecting it to do.
Send video of this naughty behavior, that may help me 
The toggle isnāt a actual toggle is it? When I said toggle you just need it to toggle a cellās value from like zero to 1 or true to false and when that value changes they go invisible, I didnāt mean an actual real toggle button. I apologize, I did say button, I was at work and distracted. I say button a lot recently, Glide overload I think.
haha, noā¦
This is how I set it up (from my earlier post):
Iāll see if I can make a video that shows the behaviour.
Okay, here is a video (I recorded this on my phone).
Notes:
- I added the āSCREEN ONEā & āSCREEN TWOā components at the top to make it more obvious what is going on. (NB: Itās the same screen both times, with component visibility being toggled)
- Youāll notice that when I tap the submit button (0:20), it initially switches to āSCREEN TWOā, and it looks like everything has worked.
- But then several seconds later (0:29) it flicks back to āSCREEN ONEā
- And then finally at 0:38 it bounces back to āSCREEN TWOā
The expected behaviour is that after I tap the submit button at the bottom of the screen, it should:
- Hide all the choice components and text components associated with SCREEN ONE
- Take me to the top of the screen
- Expose the text components associated with SCREEN TWO
- Reset all the choice components (clear values) (kindaā¦, but see below)
- Expose all the choice components in their reset state
- STAY THERE!
One thing to note is that when the choice components are unhidden, itās obvious that the āclear valuesā action hasnāt completed yet. And this is what leads me to believe there is a race condition going on.
Below is what the action sequence looks like:
2 Likes
How is you sheet setup? I would think that each question was a column and each row was a user. If that was the case your next screen would just link to same sheet but you would have it be the rest of the questions and since you stayed on the same row the action to set column would be able to set the entire row with 1 simple action. But since its multiple choice it causes the issue of thatā¦
How far aside from these choices have you gotten with the project? Do you plan on turning this into a template? If not are you comfortable with using a script instead of glide logic?
Send me a copy of the sheet, just the sheet, I just need a list of your options, I think theres a much easier way to do thisā¦Nevermind. Iām just reading them from the video.
This is what the choice options look like in the sheet:
Essentially, there are 66 pairs. Each pair fills one of the choice components.
When the selections are written back to the sheet, it looks like this:
The value in Col F indicates the āFeedback Typeā.
Columns C & D are the user that provided the feedback, and the subject of the feedback, respectively.
In the video I shared earlier, in stage 1 the user is being asked to describe how the subject āIsā, and in stage 2 they are asked to describe how the subject āCould beā. Both set of responses are written to the same sheet.
I am developing a set of scripts that will process and summarise the results.
But none of this is really relevant (as far as I can see).
No, itās a private project for a private business. No plans to ever release it as a template.
Iāll be using scripts extensively in the backend for data crunching - but I donāt see how scripts can help with what is a UI/UX issue?
Why dont you just clear the row thats dedicated to that user when they are done? Give me a few minutes. Iām building this out real fast to show you what Iām talking about.
As the user works through the choices, they are temporarily stored in user-specific columns.
Then when they hit submit, a new row is written and the user-specific values are cleared.
Clearing the row that has just been written to the sheet makes no sense, as the whole point of the screen is to create that row.
Then dont clear them just stay the pathā¦ok, just give me a moment.