- Comments (88)
RE: Enable 'total row' also to be exported.
Export subtotals and grant totals for a matrix is extremely importat for a report built on Power BI.
What you see should be what you get exported.
RE: Enable 'total row' also to be exported.
This is very important, make a fix for this error.
Users themselves cannot correctly calculate complex totals
RE: Enable 'total row' also to be exported.
Power BI runs reports, not for data dump. Total is a critical part of a report, a must have element. Please make it exportable.
Thank you!
RE: Enable 'total row' also to be exported.
Why oh why is this not available?
RE: Enable 'total row' also to be exported.
Please include this. My firm's reporting metrics rely on PowerBI. This functional issue has caused a significant bottleneck, resulting in lower synergies awarded by the software. Clients not happy!
RE: Enable 'total row' also to be exported.
Hope this issue will be fixed in the recent releases.
RE: Enable 'total row' also to be exported.
We also need this solved asap for matrices and flat tables. There are reports which have to be exported to Excel including totals. Thx.
RE: Enable 'total row' also to be exported.
Same when we export from Power BI Service, and not only matrix - plain tables should have this feature as well.
RE: Enable 'total row' also to be exported.
We need this asap. Please fix
RE: Enable 'total row' also to be exported.
I am using Direct Query per client needs/request. Only one table is used for this instance. There are NO other tables or relationships.
I have 3 visuals on the screen:
A Slicer so the user can specify a date range, a Card to display the count of rows, and the Table visual to allow the user to see and export the data.
The data being exported is missing data (rows).
The count as displayed in the Card visual is correct (verified using SQL Server Management Studio).
The total rows for this scenario is 8,172.
When I export to CSV, the total row count is 8,155.
This data is need for reporting requirements per federal regulations.
It really needs to be accurate...and consistent.
I recommended the client use Power BI instead of Tableau.