Hi everyone,
I have kind of a problem… I’m struggling with it for three days now and have no idea how to solve it… To make things easier I created a general example to explain it.
General example:
In an app a user can pick his favorite 3 generes.
If the user is quite intelligent, he will pick 3 different generes based on his preferences… But he could also pick 3 times the same one! And as we all know: If something is possible; dumb users will do it!
Same thought here. Until glide let’s us compare two column values to each other, I can’t think of a way to do this. If we could compare two column values, then I’m thinking we could apply filters on the fly.
My point is: I am working on a „Roleplay app“. And I have to match 8 Characters to 8 People. And I don’t want that two People can play the same Character, because it is necessary for the story that every Character is being played.
The example above was only to describe my problem as simple as possible
Ok, but your example didn’t represent that. It was showing the same user picking from the choice list.
I would suggest you not use a choice component and use an inline list and form combo where a column in the list could be flagged as being used by someone else. You would then need to create some kind of reset to reset all the flags back to the false state.
Only way to do this currently is to have the user submit the form three times. Each subsequent time the user goes to the form, the previous choice is disabled. Once the user had chosen three times, the form button is no longer visible. This could work, right @Jeff_Hager?
Yeah, I would think it’s possible. It would be easiest if it was just a first come first serve for character selection. Probably similar to our booking examples. Here’s my example: https://concepts.glideapp.io/. Set a choice component before the form button…use that choice to set a relation to the form responses sheet…then hide or show the form button if the choice has already been chosen or not.
If we did three form submissions, it would be similar, but a record for each user to contain the initial choice value asking with their email, then template columns in both the user and form response sheets to join email and their choice.
There could also be similar variations with relations and an if then column on the choices sheet to set a true/false value and then filter the choice based on that true/false value.