So I’m using the RadioButton element that’s provided from Bubble editor.
My question is how do I “uncheck” this? like after clicking on it, how can I unselect it and also grab its status?
Also with the search box from bubble, how would I grab the value found?
In this screen shot I searched and got this place. Now how would I like store it? Like say I wanted a text element to dynamically display the search result?
Hello @cobyhong!
Please review as follows:
Radio button
To uncheck it, empty its’ default value:
This is how it looks when previewing it with an empty default value:
To select its value, just refer to it when writing an expression. Here an example in a text field “radiobutton’s value”:
Searchbox
To grab its value you do the same as with the radiobutton. When you write an expression just refer to it as “searchbox’s value”. Here an example in a text field:
To store its value you have to have a thing in the database to store it and you also need to define what kind of thing the searchboxe houses. And you need to build a flow to do it.
I see that you may be from Manta, Ecuador. I am also Ecuadorean! Saludos!
Hope this helps! 
how would I uncheck it if someone checks it? Like if it is just one column?
You must have two flows. One with a condition if the radiobutton is checked. The second one with a condition if the radiobutton is not checked.
This way it is unchecked the you check it. If it is checked then you uncheck it.
The checking or not checking could be a yes/no. Yes for checked and No for unchecked.
Think of a radiobutton as a visual way to express a value from the dB. A thing’s value. The way you have it, is as if the radiobutton has a value. If you set the radiobutton to have a defaultvalue from the dB then things should be working. But … most likely the defaultvalue is not set by your mention that things are not working.
Try > when this radiobutton is pressed and thing’s value is yes (the thing in the dB that you want to evaluate)
However, you are trying to set the value for the radiobutton itself … mmh
I would need to know what it is exactly that you want to do, to be able to provide you with a better suggestion.
I basically want the radiobuttons to work similar to checkboxes. Like you can uncheck / check them. As of now, the radio button when just a single thing, does not allow the user to uncheck the button.
They do not work the same way
More elements come into play when using radiobuttons. When you kindly say that you want them to work the same way … falls short to what you want to accomplish.
Example; I want thing 1 with a field type y/n set to “yes” to do Y… This explains better what the use case is 
Another suggestion.
Just express the default value of dB thing (or page custom state) that the radiobutton needs to display in order to know if displays a check or unchecked status,
Then when a user clicks it build a flow that does what you want if the dB thing’s value (or page custom state’s value) is yes … and a second flow if it is no.
Hope this helps! 
can you show example, i keep trying and nothing seem to work
Hi! Perhaps this video could spark some ideas. I recommend to focus on the logic and not necessarily on the UI. This way you can apply it perhaps to the radiobutton > Bubble.is Quick Tips - Design your own Checkbox
I also found this one (have not watched it but perhaps it addresses what you need) > How to Implement Custom State with Checkboxes in Your Bubble.io Web App
@cobyhong, I think it’s very important to point out that you’re going against the native use case of a radio button.
Radio buttons are for choosing between values (essentially making it a required field) and checkboxes are for optional inputs.
Don’t go against the grain.
Radio buttons and checkboxes are used the way I have detailed above, basically everywhere and users are used to that. Changing this will confuse users, not to mention the knock on effect for users navigating the internet with screen readers and those not very internet savvy or have sight issues.
You may not expect users with disabilities and that’s fine but as I mentioned, these input elements are used for very different things and I would recommend adhering to those use cases for ease of use for your user base.
This topic was automatically closed after 70 days. New replies are no longer allowed.
