The data has separate columns for each type of program, e.g. prog1, prog2, prog3, etc.
I created separate filters for each program, because the filter is on a different column. Filter1 only displays rows with {progr1}=”yes”, filter2 is {progr2}=”yes”, etc.
I would like to have a parameter control that allows me to flip between filters. If the filters were based on the same column, that solution seems straightforward using the parameter as the filter value. But each filter is using a different column.
There are over 40 programs, so even the filters include multiple columns, e.g. filter20 is {prog20}=”yes” OR {prog21}=”yes” OR ….
I am open to rethinking this problem too. I guess the transpose (unpivot) is still on the Road Map? Thank you for any suggestions.
Hi @markusen and welcome to the Quick Sight community!
This is a pretty interesting scenario; I’d like to think that there’s a work around that can be explored in this scenario but may need a little more information. How are these program filters being implemented across your analysis and how much are they handling?
If you could provide some screenshots so that we can gain a better picture of the full scenario.
Additionally, are you familiar with Quick Sight Arena? This is a sandbox environment where you can upload copies of an analysis so that others’ can assist with issues. If you are able to upload a copy of your analysis with anonymized data, that may be the easiest way for us to further assist!
Thanks @Brett for considering this. l may have found a work around to this. I requested that the original dataset transform (unpivot) the 40+ program columns into a single program column. This bypasses the need for the 40+ corresponding filters.
Thank you for sharing the additional information! I agree that the proposed work around to unpivot the program columns into a single field would potentially be your best option. But I recently came across a similar request and proposed a calculated field that worked for his instance, and may work for this scenario as well.
It’ll may be long to setup based on the sheer volume of your program options, but could look something like:
Start by building a parameter with custom values that list each Program…’Program 1, Program 2, etc. This will be used below as ${Program}
Then you’ll use this to create an ifelse calc. field: ifelse( ${Program} = ‘Program 1’ AND {Prog1} = ‘yes’, 1, ${Program} = ‘Program 2’ AND {Prog2} = ‘yes’, 1, ${Program} = ‘Program 3’ AND {Prog3} = ‘yes’, 1, …, …, …, 0)
Then you can assign a filter to your visuals based on this calculated field that only shows values that equal 1.
Let me know if that could serve as a work around for your case or if you have any additional questions.
Hi @markusen,
If you hover over the portion of the syntax that has the red line underneath, what is the error code that pops up?
I have a feeling this has something to do with the parameter being multiple values as opposed to single value. Let me test out some additional things knowing that this is a multiple value selection to see if it’s still possible.
