Export Visualization as .csv

[jarwest]

Hey all,

I have a report that contains a table along with some slicers. I need to find a way to export this table as a .csv, but so far the only methods I have found require creating a dashboard, none for getting a .csv frm a table within a report. Does anyone know of any solid methods I could use to get the .csv file out of a table?

I hope you all are staying well, any help is appreciated!

[v-zhangti]

Hi, @jarwest 

There are several ways to export .CSV files.

• Export data from a visual on a dashboard

• Export data from a visual in a report: Summarized data is available in the Power BI service as .xlsx and .csv and in Power BI Desktop as .csv.

Power BI report designers control the types of data export options that are available for their consumers. The choices are:

• Allow end users to export summarized data from the Power BI service or Power BI Report Server

• Allow end users to export both summarized and underlying data from the service or Report Server

• Don't allow end users to export any data from the service or Report Server

Considerations:

The maximum number of rows that Power BI Desktop and Power BI service can export from an import mode report to a .csv file is 30,000.

This is the relevant document, hope to help you:

https://docs.microsoft.com/power-bi/consumer/end-user-export 

https://docs.microsoft.com/power-bi/visuals/power-bi-visualization-export-data 

Best Regards,

Community Support Team _Charlotte

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[lbendlin · Accepted solution]

That doesn't sound right.  On your table visual click the ellipsis (...)  and then Export Data.  

Then click "Summarized Data" and select the csv option.

Note the row limitation.  If you don't like that you can run your own DAX query that is equivalent to the one used to render that particular table visual.

[jarwest]

This is what I was looking for and the solution I ended up going with. I initially was looking at this issue all wrong, thank you.