1 of 1 people found this helpful
Though I have not done this myself, I have come across threads on this forum that discusses the need and approaches you could take. You can see one discussion here.
Hope it helps
Thanks, Siraj. While that particular thread doesn't quite address the need, I will continue combing the archives for past wisdom on the topic. Much appreciated.
This is a solution I have used to filter across multiple sources. It does not allow for multiple selections, but does have the all selection. You can see the variable that I created and added to each source that is connected to the same season parameter. Let me know if this gets you an closer to what you need.
Possible Solution.twbx.zip 921.8 KB
Thanks very much. I've been playing with filter actions, but this is much closer to what I was trying to create for a user experience. That "all" selection option is what I really needed to replicate.
I'll apply this method to my workbook, and I think that will be the best solution.
I've voted "up" on the need for a multi-select parameter.
Much, much appreciated!
You could create an cross reference table in your SQL/backend db. Then, match the values to the parameter. I tend to use floats for ease of use, so if I have multiple field names that are semantically the same thing, but named differently in different data sources, I join all the datasources to the XREF and then pull them with the one parameter:
E.g. CASE parametername WHEN 1 THEN [XREFFieldname]. The XREF could be joined to dept, dpt, department etc.
I ran into a similar situation where I needed an "ALL" filter option on my parameter. Because I needed the parameter to filter the dimensions shown in the worksheet as well as the data, I couldn't just add in the logic to individual measures. Instead, I came up with this workaround.
Create a parameter that lists each value of the dimension, and then a final row where you manually type in all the values on one line. I.E:
Program A, Program B, Program C (change alias to "ALL")
Now create a calculated field as follows:
Contains([Parameter],[Dimension to Filter])
Use the calculated field to filter for 'True". If values in the dimension have similar names, you may need to mess with the strings to make them unique. The two significant limitations to this approach are 1) the last line of your parameter can get too unwieldy if you have a lot of values in your field and 2) these string calculations definitely suffer performance limitations. Still, if you're in a bind and you need to filter a visible dimension in multiple data sets using a parameter, this may just be the work around you need.
Using the 'All' solution is good in a lot of cases, but what about when you need a parameter to select for two or more values, but not 'All'.
I have found myself using charts or tables as 'parameter controls' and using dashboard actions to allow for multi-selects.