So I’m having trouble getting validations driven by conditional statements to work properly. I’ve ben playing with this for more than an hour and I just can’t figure it out.
From the dropdown “Gender” I choose “Women Only” and enter a color in the drop-down “Women”… I get this result: The ‘Go to Next Page’ button turns blue as expected.
From the dropdown “Gender” I choose “Men & Women” and enter a color in both drop-downs… drop-down “Men” and drop-down “Women”… I get this result: The ‘Go to Next Page’ button turns blue as expected.
From the dropdown “Gender” I choose “Men Only” and enter a color in the drop-down “Men”… I get this result: The ‘Go to Next Page’ button does NOT turn blue as expected.
Hi there, @tom.love1250… without being able to see what’s going on under the hood, it is going to be difficult for anyone to help here. Can you share some screenshots of the conditionals and workflows?
@tom.love1250 I agree with Mike it’s gonna be easier if we can see your editor.
However, while testing the page I did notice that the page is doing actions every time you select a new item in the dropdown. You don’t need to do this to change the color of the “Go to Next Page” button. You simply need a conditional saying When: Women dropdown is not empty, then this buttons color = XXXXXX
I just took a look at it and I’m really confused. What are color dropdowns supposed to be doing? Make the app editable by anyone and share the link so we can take a look at the backend.
So I have a number of things going on here. For example, when Men Only is selected, I want to force the user to make a color selection for men before moving on to the ‘next page’. In this example, I also want to disable the Women Only dropdown. The main thing is I want to turn the button purple whenever a condition is not met.
I thought that conditions process in the order in which they are organized from top to bottom. Isn’t that why conditions can be moved up or moved down? If the first conditional does not apply, Bubble moves to the second conditional and so on. Do I have that wrong?
If I am seeing things correctly (which could easily not be the case), that whole thing looks a lot more complicated than it needs to be (which is what bubblealex was saying without even seeing the editor). You’ve got dropdowns, groups, and workflows all interacting (I think) for what should be the simple act of enabling a button.
I took the liberty of creating a page called example, and the page is just 3 dropdowns and a button (with conditionals on the button), and I believe it is working the way you want (minus changing the color of the button, but you can figure that out, and it’s really about whether or not the button is enabled). Anyway, check out that page and see if that is what you had in mind.
Oh, and I used options sets for the dropdowns, and I would go that route if I were you. If you want to get rid of the example I created, simply delete the example page and the option sets, and pretend I was never here.
Yup Mike’s example is exactly what you want to do. I also added some conditionals on the other dropdowns to hide/show based on the first dropdown’s selection. Much more user friendly. Take a look.
