I have the following scenario. let me explain you the current setup in case this helpa to understand the issue. I mostly want to understand if there is a workaround.
QS dataset: This includes dataset parameters.
QS Analysis: This includes 3 filter.
Scenario A(This works): In the analysis: Cascading filters enabled
These filters(values) are from a single QS dataset(SPICE)
Select region ‘EU’,
Select country(I select 2 values out of three: So I select ‘BE’, ‘DE’ and I excluded from the selection ‘ES’).
Select merchant id: I select one value
—> This works, I get some values back.So I see values in an analysis table.
Scenario B(This doesn’t work): In the analysis: Cascading filters enables
Select region ‘EU’,
Select country(I select all values: So I select ‘BE’, ‘DE’ and ‘ES’).
Select merchant id: I select one value
—> This does’nt work.
I want to understand why this happens and if there is a workaround.
I ran into an issue using the parameter selections in a calculated field. Initially when you open the analysis you may have the parameter set up as a String list ( BE, DE …). Later on when you change the Selections and do a Select All I observe that things change to “All” in the parameter.
While I am not sure if that is the case here you may want to check how you are applying the filter in your dataset. Individually selecting the three values may work and it may also work if you do a Reset on the analysis which will make the Select All to be treated as a String list.
Yes, so I am pretty sure this is my scenario. When I select the three values the filter/control change to ‘All’. Is this the reason of the issue?
I dont understand this part: “Individually selecting the three values may work and it may also work if you do a Reset on the analysis which will make the Select All to be treated as a String list.”
In my particular case I have a QS dataset that contains a parameter in the WHERE clause, so I want to put all the countries selected into that parameter(so the user might select 1,2 or 3). 1 is fine, 2 is fine, 3 cause the error.
Hi @jgrueso,
It’s been awhile since last activity took place on this thread, are you still encountering the same issues or were you able to find a work around?
If so, could you include some screenshots to show how the error is taking place?
If we do not hear back within the next 3 business days, I’ll close out this topic.
Here’s an example of what I mentioned earlier. This is a case from my dataset and you need to adapt it to your case.
The IN(NULL, … ) case in my screenshot addresses the situatio where the Select All is done by the user in the parameter.
Similar to this you can have a boolean result (1, 0) come out of your ifelse and the where clause only looks for where the result = 1 (True) to filter your records.
