This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
General Discussions has some can't miss conversations going on right now! From conversations about automation to sharing your favorite Alteryx memes, there's something for everyone. Make it part of your community routine!
Solved! Go to Solution.
Hey @mst3k,
I had this same issue a few months ago when I was developing an app with 5 radio buttons and I wanted each to enable a container instead of disabling it. Essentially I had to build 4 actions for each radio button to disable all of the 4 other containers that I did not want to run for each radio button (total of 20 actions). I definitely think this is a great idea to be added to the ideas forum!
Hi @mst3k an alternative is you use a condition tool with your interface like below and this setup when the radio button is selected will enable the correct tool container.
Hey @mst3k, I actually have a small change to your solution that lets you keep your containers open. If you update your formula to be the following, you get the correct functionality while being able to keep your containers enabled.
IF [#1] == "True" THEN "False" ELSE "True" ENDIF
It worked with my 3 radio buttons but I figure it should scale for any number.
Thanks for asking your question, it got me close enough to figure this out.
Action Configuration
Selection for Debug
Result of Debug
awesome! I didn't even think of using an actual formula in the "update with a formula" option, just kept thinking of a string/literal. this is my first project working with the interface tools.
thanks!