Archived from the Bravo community forum (2021–2026). Some answers may refer to older versions of Bravo.
Hi,
I have a form that I would like user to submit, as part of that form submission they need to toggle a switch to yes or no.
I have a component I created with two variants, yes or no toggle.
I layered the two variants of the component on top of each other, following this doc.
However, as soon as I add the bravo tag [state-set:reminder] into the group name two things happen.
- The toggle disappears from bravo vision although I see it in the binding screen.
- Bravo vision shows me two versions of my container.
I'm thinking the first problem might have something to do with the fact that the doc I'm following is for patching an existing record for a like button, while I'm trying to patch a record that has not been created yet...
No idea why second problem is occurring.
Has anyone ever encountered this problem before when creating a toggle for their form?
What did you find that helped you fixed the problem?
4 replies
Hey I never tried to implement a toggle but generally speaking the refresh tag is not always so reliable, so if the state visibilty of a component changes while you are looking at the same screen, UI binded elements may just hold their initial visibility status. For this reason it is not already convenient to operate in this manner.
What do you mean by saying the record was not yet created? the only thing it matters is if there is an object in your server containing the visibility true or false value binded to the UI element
Also how can Bravo vision show the two versions if they are on top of each other?
have you tried using [input-state-set:xxx] instead of just [state-set:xxx] ?
See https://docs.bravostudio.app/bravo-tags/form-and-input-fields/stateful-input-checkbox for an example
I haven't set any visibility conditions for the toggle. I have left that field as none.
I layered them on top of each other per the documentation. Bravo then uses action:remote tags to trigger change in state.
Yeah I tried using both of those.
I did follow up with Bravo and they are saying that my set up is correct so it may be something on their end.
Feeling like it should be quick fix now that they are running some tests on their end.
did you get this resolved? I'm running up against the same error with the state set not being visible at all in Bravo Vision but it shows up in the binding screen
Wrote something in this thread and want it removed? Request removal
Ask the community on Discord
This archive is read-only. New questions, office hours and product updates now happen in the Bravo Discord.
Join the Discord