Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
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.
User | Count |
---|---|
25 | |
12 | |
8 | |
6 | |
6 |
User | Count |
---|---|
26 | |
12 | |
11 | |
9 | |
6 |