Turning filters on/off using Alteryx In-DB tools in app

[bryanbumgardner]

Hello,

I am trying to create a customized app that pulls In-DB information and dynamically filters it based on some criteria.

Imagine that my data has three columns: Campaign, Strategy, and Concept Name. 

There are several campaigns, a handful of strategies within each campaign, and thousands of concepts within each strategy. 

It was easy to create a list box to control an In-DB filter that allows the user to pick specific campaigns and strategies. Problem is, there are thousands of concepts in each strategy and selecting them from a dynamically generated list box is difficult. I am going to allow users to upload a file with all their concepts names and I can create the filter from that file.

Here's my Alteryx problem: If a user wants to select ALL concept names within a strategy and campaign combination, how can I turn off the filter to allow all the concept names through the In-DB query. I'm stuck.

Any help is appreciated! 

[MarqueeCrew · Accepted solution]

K.I.S.S. the problem.

Use a radio button to allow for selection of the filter options.  If the button is unchecked, route the app through a different SQL path than if it is checked.  2 sets of logic controlled by the user's choice.  Yes, this has more logic to support, but it is straight-forward.  You could embed the SQL into an action tool otherwise and replace the filter with something like:  "Where 1 = 1" if they choose all.

Cheers,

Mark

[levell_x_dunn]

Hi @bryanbumgardner

I concur with @MarqueeCrew, KISS is the answer.

It's more initial work on you, buy building two different paths, one with a filter and one with all the data, and then build a radio button for the options, but it allows your end user to have that option.

As you can see below we added multiple radio buttons that give the end user different choices to select based upon what they need

[MarqueeCrew]

If a radio button contains the interface group for the list box and that is deselected, you can action to update the filter to 1=1 or just 1. 

Keep the filter just make it true. 

[bryanbumgardner]

Sorry it took me so long to respond! 

I've kind of tried something like that, where filters will be ignored if specific radio buttons are deselected and tool boxes disabled with it. 

But I cannot have interface tools inside disabled tool containers. I'm trying to figure out a good structure for this and I can't find any examples.

Basically, I'm trying to offer four radio buttons, and whichever one they pick will open a bunch of sub-query interface questions. How can I structure that in a way that works properly?