Like the title says. It seems like every other field element allows you to just take it’s value and store it in a related data field. But with check boxes you need to get custom states or list or other approaches involved to get a simple ‘yes’ ‘no’ (true or false) updated in the data table.
I’ve been working my way through learning Bubble coming from more of a coding background but being more of a visual builder, which means I like Bubble a lot.
Things have been going great until I got to this point. I understand that there other use cases for checkboxes but the functionality at the moment goes against what seems like common practice in so many other development platforms.
Forgive me if I’ve missed some thing but after reading through the forum posts I’m still a little confused behind the reasoning and functionality.
I have a form with multiple check boxes and I want to store the value of each check box in an independent field. I don’t want a separate workflow action based on a custom state or if the checkbox is checked or not.
Sorry for the long write up. I feel like I have to be missing something and have been frustrated trying to get this to work.