Hi guys, pretty new to bubble so I hope my question is not too basic. I am building a platform where you can buy and sell tickets.
In bubble i have a data type called tickets. On the page where you want to sell tickets, and a new ticket entry is created once you do that i have the following buttons and fields: a input field for the number of tickets you want to sell, which is default 1, minimum value is 1 and max value is 5. Also i have a plus and a minus button which change the value of the number of tickets. I also have a group in which there are 2 checkboxes, they only appear when the value of the number of tickets is higher than one. One checkbox is for when you want to sell your tickets separately and the other checkbox is for when you want to sell the tickets together. In the database i have a data type under tickets, that is called “together” and this is a yes/no data field, the default value is set to be no. In the workflow i have the following logic: when the value of the checkbox together is changed and the checkbox is checked in the database the field together returns the value yes. When the other checkbox changes its value and is checked, the together data field returns no. The problem is that whenever i try, in the preview mode, and then i go to the database to check the app data the value of together is always no, i can’t figure out what the problem is.
Thanks in advange!
Hey, if possible please do attach the screenshots of the workflows you are using that would help better to understand.
But I think better approach would be to change the DB values when the user have bought the tickets (this would help with your extra workflow usage) and you can use the states to store temp values or you can also use the direct values of checkbox in workflows as well. 
Hope that makes sense.
I’ve attached a few screenshots, I hope it makes sense bc it is partly in romanian language. I don’t think it would make sense to change the DB values when the tickets get purchased.
The logic behind this is as following: a user wants to sell a ticket/ more tickets. He will first create the listing of the ticket/ tickets. If he wants to sell the tickets separately or together, that will influece how the tickets will appear in the "buy tickets"section of the platform. Basically if the seller wants to sell them together in the "buy tickets"section a buyer wont be able to buy only one ticket from him, he must buy the entire amount of tickets. So I need the database to have the yes/no field in order for the listing to be accurate.
Or at least that’s how it works in my mind 
the field called impreuna_y/n is the field that I am reffering to as together data field, which is the yes/no field.
Thanks!
Ahh, it seems you are navigating on different pages so in that case yes you can save it in DB.
One thing I would double check on Step 2 if you are pointing towards the right DB to change the thing ? Based on the workflow it should be updating it.
Otherwise do message me in private and you share the link of the app and I can have a look on that.
