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.
Find answers, ask questions, and share expertise about Alteryx Designer.
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!
I'm making an app with radio buttons to give 3 different paths of using the tool. I don't want to mess with blank inputs and other errors for the paths they aren't using since there's no inputs there. I thought I could do this by putting each path in a container in the workflow, then link the radio button to the container. What I want to happen seems logical - if that is the radio button they've selected, it should run that path (keep it enabled). Instead the action seems to work the exact opposite of what I want. It says "If the Check Box or Radio Button is selected, the Tool Container will be disabled". Why would you want to select a radio button choice to have it only DISABLE something? How could you even set up a 3 or 4 radio button question to perform different actions then? I don't see any option in the Action button to make it enable instead of disable, which would have been nice. Is the only option to disable all my containers, and then use the Action to update the "disabled" property to False instead of using the default action?
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!
The more buttons you add the more links you'd have to do exponentially or something like that right? Painful! For now I was able to get what I wanted by disabling every container, then from each radio button's Action tool I set it to "Update Value with formula" and changing the container's disabled property to "False" when the radio is selected. I still think this is the logical opposite of what you'd expect a radio button to do. I don't like having every container collapsed/disabled because it makes it harder to develop and debug the workflow, but I settled on that for now. Might be less painful for you than linking every radio to every other 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.