Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
In the table visual below I have 5 rows returned, which I believe to be correct. (See filters applied to table). I am expecting my measure 'CR Count' to also return a row count of 5 ; however, it appears to ignore the 'dw HSECaseCategoryDim'[Col Value] filter and returns 43.
What am I missing 😞
Solved! Go to Solution.
Turns out that it was my relationships that were wrong. This worked in the end.
From your relationship diagram, you can see that the table 'dw HSECaseCategoryDim' does not filter 'dw HSECaseDim' nor does the reverse hold. They both filter the bridge table but not each other. In particular, the filter on 'Col Value' has no effect on the measure since it counts the rows of the fact table (which aren't filtered by 'Col Value').
The best option would probably be to flatten those dimension tables into a single one so that you have more of a star schema rather than a snowflake schema.
Very interesting. Why does the filtering appear to apply in the table visual in my report?
When I add the 'dw HSECaseOccurenceFact'[HSEDimKey] , (880 rows)
When I add and filter 'dw HSECaseDim'[Corporate Reportable Flag] = True , (43 rows)
When I add and filter 'dw HSECaseCatgeoryDim'[Col Value] = "Loss of primary containment (HCRs)", (5 rows)
And can I harness this in a measure?
Thanks again.
Turns out that it was my relationships that were wrong. This worked in the end.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
21 | |
15 | |
14 | |
11 | |
7 |
User | Count |
---|---|
26 | |
24 | |
12 | |
11 | |
10 |