Export the data that was used to create a visualization
To see the data that's used to create a visual, you can display that data in Power BI, or export it to Excel. This article shows you how to export to Excel. Data can be exported to Excel from a Power BI dashboard tile and from a report visual.
Not all data can be viewed or exported by all users. There are safeguards that report designers and administrators use when building dashboards and reports. Some data is restricted, hidden, or confidential, and cannot be seen or exported without special permissions. If you are a designer or admin, select the tab below for Admin and designer controls for exporting.
Who can export data
If you do have permissions to the data, you can see and export the data that Power BI uses to create a visualization.
If you don't have permissions to the data, you won't be able to export or open in Excel. Often, data is confidential or limited to specific users. For details, see the Considerations and limitations section at the end of this document. If you are working in the Power BI service, you can contact your Power BI administrator or you can look up the contact information for the dashboard owner to request export permissions. To find the owner, select the dropdown next to the report title.
Viewing and exporting data
Watch Will export the data from one of the visualizations in his report, save it as an .xlsx file, and open it in Excel. Then follow the step-by-step instructions below the video to try it out yourself.
This video might use earlier versions of Power BI Desktop or the Power BI service.
Data is protected when it's exported out of Power BI
Report owners can classify and label reports using Microsoft Information Protection sensitivity labels. If the sensitivity label has protection settings, Power BI will apply these protection settings when exporting report data to Excel, PowerPoint, or PDF files. Only authorized users will be able to open protected files.
Security and Power BI administrators can use Microsoft Defender for Cloud Apps to monitor user access and activity, perform real-time risk analysis, and set label-specific controls. For example, organizations can use Microsoft Defender for Cloud Apps to configure a policy that prevents users from downloading sensitive data from Power BI to unmanaged devices.
Export data from a Power BI dashboard
Open a dashboard in the Power BI service and select a tile with a visual.
From the upper right corner of the tile, open the More options (...) dropdown and select Export to .csv.
If the tile was pinned from a report with a sensitivity label, you'll see this warning. Consider the sensitivity of your content before deciding whether to export or not.
Power BI exports the data to a .csv file. If you've filtered the visualization, then the .csv export will be filtered as well. Your browser will prompt you to save or open the file. By default, your export is saved to your local Downloads folder.
Open the .csv file in Excel.
Considerations and limitations
These considerations and limitations apply to Power BI Desktop and the Power BI service, including Power BI Pro and Premium.
There are many considerations related to exporting to Excel. This is one of those features that report designers and Power BI administrators may disable for individuals or even for an entire organization. They do this to ensure that private data isn't exposed to the wrong audience.
If you find that you are unable to use this feature, reach out to the report owner and your administrator to understand why you are unable to export data from a particular visual or from all visuals. It may be that this feature has been purposely disabled and perhaps they can enable it for you. Other times, there may be particular reasons an export does not work. It could be related to permissions, data contents, data type, visual type, how the designer named the fields, and more. When contacting the report owner or administrator, refer them to these articles: Admin tenant settings, Row level security, and Data protection.
When exporting data to Excel, the speed of download of the generated workbook can vary depending on network bandwith.
The maximum number of rows that Power BI Desktop and Power BI service can export to a .csv file is 30,000.
The maximum number of rows that the applications can export to an .xlsx file is 150,000. The actual number may be lower than 150,000 depending on query limits and visual types.
- For export from matrix visuals using Data with current layout, the export limit is 150,000 data intersections. For a table visual, each row has 1 data intersection. For a matrix visual, each row can have 1 or more data intersections, so the exported rows count can be less than 150,000. (For example, if a matrix visual has 3 data intersections per row, the maximum row count will be 150,000 / 3 = 50,000 rows.) The message "Exported data exceeded the allowed volume. Some data may have been omitted." will be added at the footer of the Excel file when the limit is hit. Consider limiting the dimensions or filter the data to avoid this scenario.
Export using Underlying data won't work if:
the version is older than 2016.
the tables in the model don't have a unique key.
an administrator or report designer has disabled this feature.
you enable the Show items with no data option for the visualization Power BI is exporting.
For export from matrix visuals using Data with current layout, consider the following:
Matrices with columns and/or values but no rows will be exported as having rows and/or values but no columns
Matrices with only one row and/or values but no columns will be exported as table (no right border separator)
If the Show on rows toggle is set to 'On' in Power BI Desktop for a table or matrix visual, the visual format would not be preserved when data is exported to Excel
If the Row subtotals toggle is set to 'Off' in Power BI Desktop for a matrix visual, but the matrix visual has expanded and collapsed sections, exported data will contain subtotals for rows. To work-around this issue, use the Expand | All command from the visual's context menu.
When using DirectQuery, the maximum amount of data that Power BI can export is 16-MB uncompressed data. An unintended result may be that you export less than the maximum number of rows of 150,000. This is likely if:
There are too many columns. Try reducing the number of columns and exporting again.
There's data that is difficult to compress.
Other factors are at play that increase file size and decrease the number of rows Power BI can export.
If the visualization uses data from more than one data table, and no active relationship exists for those tables in the data model, Power BI only exports data for the first table.
Power BI custom visuals and R visuals aren't currently supported.
In Power BI, you can rename a field (column) by double-clicking the field and typing a new name. Power BI refers to the new name as an alias. It's possible that a Power BI report can end up with duplicate field names, but Excel doesn't allow duplicates. So when Power BI exports the data to Excel, the field aliases revert to their original field (column) names.
If there are Unicode characters in the .csv file, the text in Excel may not display properly. Examples of Unicode characters are currency symbols and foreign words. You can open the file in Notepad and the Unicode will display correctly. If you want to open the file in Excel, the workaround is to import the .csv. To import the file into Excel:
Go to the Data tab.
Select Get external data > From text.
Go to the local folder where the file is stored and select the .csv.
When exporting to .csv, certain characters will be escaped with a leading ' to prevent script execution when opened in Excel. This happens when:
- The column is defined as type "text" in the data model, and
- The first character of the text is one of the following: =, @, +, -
Power BI admins can disable the export of data.
If a dynamic format string is applied to a measure, the exported data won't preserve this formatting in Excel. Also, visual-specific formatting such as percent of grand total for a measure isn't preserved in Excel.
More questions? Try asking the Power BI Community
Submit and view feedback for