The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
I'm trying to dynamically apply a filter statement in DAX using the IN operator. By passing in a string of members to filter on.
In my scenario the fact table and DIM table do not have a relationship. After applying a context filter on DIM_VIEW[View] I want the selected members to be used to filter the fact table. Without relating the tables is this possible in DAX?
The DAX code below works when I filter one member however, it doesn't like multiple selections. The concatenatex() line correctly generates the member list but the IN operation does accept a dynamic input if there's more than one selection.
VAR onemember = "View1"
VAR multiplemembers = """" & CONCATENATEX ( VALUES ( DIM_VIEW[View] ), [View], """" & ",""" ) & """"
RETURN
VALUE (
CALCULATE (
SUM ( FACT_TB, [amount] )
)
// one member - works
//,FACT_TB[View] IN {onemember}
// multiple members - does not work
,FACT_TB[View] IN {multiplemembers}
)
Solved! Go to Solution.
Hi @andymcgurty
Try the below.
Measure =
VAR __view = VALUES( DIM_VIEW[View] )
RETURN
CALCULATE(
SUM( FACT_TB[amount] ),
FACT_TB[View] IN __view
)
or a version with TREATAS for better performance
Measure =
VAR __view = VALUES( DIM_VIEW[View] )
RETURN
CALCULATE(
SUM( FACT_TB[amount] ),
TREATAS( __view, FACT_TB[View] )
)
Hi @andymcgurty
Try the below.
Measure =
VAR __view = VALUES( DIM_VIEW[View] )
RETURN
CALCULATE(
SUM( FACT_TB[amount] ),
FACT_TB[View] IN __view
)
or a version with TREATAS for better performance
Measure =
VAR __view = VALUES( DIM_VIEW[View] )
RETURN
CALCULATE(
SUM( FACT_TB[amount] ),
TREATAS( __view, FACT_TB[View] )
)
Hi @Mariusz
I have an issue when using this approach with time intelligence functions. It doesn't filter the correct values at the row level when the filter is selected for multiple members. It works fine if for example DIM_VIEW[View] is used as a dimension (on rows or columns) in my analysis because it can slice the values into their own buckets and know what dates are relevant for each view. While this works at the member level, the grand totals are wrong.
If all the members are selected as a filter, it aggregates the values up incorrectly without taking the individual D_VIEW[View] members into context, so the same result as the grand total is displayed.
I've managed to return the correct results in a DAX query however, I've been unable to translate this into a valid measure in my analysis that can apply the correct filtering.
Thanks
Andy
good work @Mariusz !
TREATAS() is exactly what I was looking for and is working with context filters in my analysis.
Thanks
Andy
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the June 2024 Power BI update to learn about new features.
User | Count |
---|---|
41 | |
33 | |
20 | |
16 | |
15 |
User | Count |
---|---|
56 | |
51 | |
36 | |
35 | |
31 |