Forum Discussion
Dynamic Parameters ( Multiple parameters that talk to themselves ) EG: Plant-Line-Material
Community Championso what does your data model look like in dq? ie. are you pulling from two separate dimensions? maybe there is a dax measure you can use a flag with isfiltered placed on the filter pane to get the correct scope and have some calculation logic in there that triggers the fact that understand the relationship inbetween to reduce what you bringing back in the slicer.
sometimes a use case calls for unconvential methods, maybe you could create a table with distinct values of that plant / station combination using a snow flake? Or maybe its even worth denormalising the tables if the performance and user experience is that unpleasant?
been a long week so my brain might not be working.
there are also ways of optimising your back end depend on what db you are using.
I'm trying to find out basically if I can create a list with more than 1 column so that the customer can cascade the chosen filters. And then, inject them in the right places of the SQL.
- vanessafvg
when you say a list? is there always a particular flow to it and so for example you have 4 filters?
user filters filter 1, that then filters 2-4 where 1 is related?
or
user filters filter 1, that filters filter 2, user selects from filter 2, that filters filter 3 etc?
second option. The user filters Plant from a distinct list. The selects Station from a distinct list. Then select a start date and then an end date. All slicers get data from a unique list that has distinct values for all 4 lists. And the lists are created with "select distinct from "whatever tables I have with dimensions" "