Forum Discussion
Row Count Not Matching
ghouse_peer - it is possible that there are duplicated rows in your Fact table, and power bi is condensing these into 2 rows in the table visual.
You can check this by setting each column in your table to "Don't Summarize":
If this does not resolve thngs, we'll need to know more about your model.
also COUNTROWS([Tablename])+0 - will be incredibly bad for a direct query table on the basis it will need to run a query over every single row of your table to establish the 0 result. here's an article explaining how bad it is for performance: https://blog.crossjoin.co.uk/2024/07/07/dax-measures-that-never-return-blank/
and some suggestions for the best way to fix it: https://blog.crossjoin.co.uk/2024/11/03/different-ways-to-replace-blanks-with-zeros-in-dax/
If I answered your question please mark my post as the solution, it helps others with the same challenge find the answer!
ghouse_peer - it is possible that there are duplicated rows in your Fact table, and power bi is condensing these into 2 rows in the table visual.
You can check this by setting each column in your table to "Don't Summarize":
If this does not resolve thngs, we'll need to know more about your model.
also COUNTROWS([Tablename])+0 - will be incredibly bad for a direct query table on the basis it will need to run a query over every single row of your table to establish the 0 result. here's an article explaining how bad it is for performance: https://blog.crossjoin.co.uk/2024/07/07/dax-measures-that-never-return-blank/
and some suggestions for the best way to fix it: https://blog.crossjoin.co.uk/2024/11/03/different-ways-to-replace-blanks-with-zeros-in-dax/
If I answered your question please mark my post as the solution, it helps others with the same challenge find the answer!
Thanks, its working. And yeah we should avoid +0 using in direct query. Thanks for the info
