Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
I have one fact table connected using Direct Query. and then created 2 calendar tables and one Table which has LE which is numeric.
now in advance editor for all these three we have created parameter linking to the respective date and LE coulmn in Fact column and all are in TEXT format.
parameter is such a way that when its null or noting is selected it should be current date else whatever the value is selected by the user.
and LE is defaulted to 732 if noting is selected. else whatever the value user selects.
now i have used table visual and selected the columnn which are required from fact table.
i have used the measure =COUNTROWS([Tablename])+0.
i have taken this measure in card visual.
now Table visual is showing 2 rows and Card visual i,e measure is showing as 7.
please let me know how to resolve this.
Solved! Go to Solution.
@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
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 152 | |
| 130 | |
| 109 | |
| 79 | |
| 54 |