How to Export Data from Table View in Power BI
Need to get your data out of a Power BI table into somewhere else, like Excel or a CSV file? You're in the right place. Power BI is fantastic for creating interactive reports and dashboards, but sometimes you need a static copy of the data for ad-hoc analysis, sharing with a colleague, or use in another application. This guide will walk you through the different ways to export data from a table view in Power BI, highlighting which method to use for your specific goal.
Reasons to Export Data from a Power BI Table
Before jumping into the "how," it's helpful to understand the "why." While the goal is to keep analysis within Power BI's dynamic environment, there are plenty of legitimate reasons to export your data:
- Collaboration with Non-Power BI Users: Your colleague in finance might be an Excel wizard but may not have a Power BI license or the training to navigate your report. Exporting to a format they know keeps things moving.
- Deeper, Ad-Hoc Analysis: Sometimes you want to mash up a portion of your BI data with other data sources in Excel or run some one-off statistical analysis that is easier to perform in another specialized program like R or Python.
- Archiving or Auditing: You might need a snapshot of your data from a specific point in time - like the end of a fiscal quarter - for record-keeping or compliance purposes.
- Seeding Other Systems: Occasionally, a simple data export is the quickest way to upload a customer list into a marketing automation tool or prepare data for a presentation slide deck.
Understanding your reason for exporting will help you choose the best of the following methods for the job.
Method 1: Exporting Directly from a Visual
This is the most common and straightforward way to get data out of Power BI. It lets you export the data displayed in a specific table, matrix, or chart directly from your report view.
Here’s the step-by-step process:
- Open your Power BI report and find the table or matrix visual containing the data you want.
- Hover over the visual to make its options appear. In the top-right corner of the visual, you'll see a small ellipsis (...), also known as the "More options" icon.
- Click the ellipsis to open a dropdown menu. Select Export data.
At this point, you'll be presented with a dialog box that gives you a few very important choices that determine what kind of data you'll receive.
A Crucial Choice: Summarized vs. Underlying Data
This option significantly changes the output of your export, so it's essential to understand the difference.
Exporting Summarized Data
What it is: "Summarized data" exports the information exactly as you see it in the visual. It respects all the aggregations (like Sum, Average, Count), filters, and structural choices that have been applied and exports just what is being shown on screen to either a .csv or .xlsx (Excel) file of up to 150,000 rows. If you see monthly sales sliced by product category, that’s exactly what you’ll get in your file - the same summarized rows and columns.
When to use it:
- When you need a clean, simple report that matches the visual for a presentation or email.
- When a stakeholder just needs the high-level numbers and doesn't care about the individual transactions that make them up.
- When you're sharing a snapshot with someone who asked, "Can you just send me what I'm seeing on the screen?"
Exporting Underlying Data
What it is: "Underlying data" exports the summarized data from your visual plus the raw, record-level data rows from your dataset that were used to calculate those summaries of up to 150,000 rows. In our monthly sales example, an underlying data export would give you the summarized totals for each product category per month, and it would include every single individual sales transaction that falls into those categories.
Note: The ability to export underlying data can be restricted by your Power BI administrator or the report creator. If you don't see this option, it's likely a permissions issue. The total record size of your export is capped, and you might receive an error message or get an excerpt if your requested dataset is too large. There could be additional hidden files behind your visual which may end up in your final export. It may be surprising if you're not anticipating it beforehand.
When to use it:
- When you or a colleague need to perform an audit or double-check the figures by looking at the raw transactions.
- When you want to feed the detailed data into another system for more granular analysis.
- When your goal is not just the "what" (the summary) but also the "why" (the detail behind it).
Method 2: Copying Data from the Data View
If you don't need a formal export and just want to quickly grab an entire data table from your model, you can do so directly from Power BI Desktop's Data View.
This method bypasses the live report entirely and pulls data straight from the source tables in your model before any summarization.
- Open your report in Power BI Desktop.
- On the left-hand side of the screen, click on the icon that looks like a spreadsheet to go to the Data view.
- In the Data pane on the far right, you'll see a list of all tables in your data model. Select the table you wish to copy.
- The data for that table will now appear in the main window. Right-click on the table name in the Data pane (or click the ellipsis next to it) and select Copy table.
- The entire table's contents are now on your clipboard. Open a blank spreadsheet in Excel or Google Sheets and paste (Ctrl+V or Cmd+V).
Pros: This technique is fast for getting a full, raw, unfiltered table of data out of your model. Very useful for digging into calculated or DAX columns.
Cons: It’s a purely manual action and not very practical for very large tables, as the copy/paste can be slow or even fail in Excel. Any report-level filters or relationships with other tables are ignored, so you are only getting the raw data from that one specific table.
Method 3: Advanced Approach with Analyze in Excel
"Analyze in Excel" is arguably the most powerful way to work with Power BI data inside of Excel. Instead of a one-time static export, this method creates a live connection from an Excel workbook directly to your Power BI dataset. This lets you and your team build custom PivotTables, PivotCharts, and formulas in Excel that pull the latest, freshest data directly from the cloud.
You’ll need either a Power BI Pro or a Premium Per User (PPU), this feature is available in the Power BI service (the browser version), not the Desktop app.
- Go to app.powerbi.com and sign into your account.
- Navigate to the Workspace that houses the dataset you want to analyze.
- Find your dataset in the list (it might be under the "Datasets + dataflows" tab). Click the ellipsis (...) next to its name and select Analyze in Excel.
- Your browser will download a small .odc (Office Data Connection) file. Click to open it.
- If prompted with a security warning, click Enable. Excel will open a blank worksheet with a new PivotTable. Notice the PivotTable Fields pane on the right - it contains all the tables, columns, and measures from your Power BI dataset!
From here, you can drag and drop fields to build tables and charts just as you would with any other PivotTable, with the difference being that your data is coming live from Power BI's curated, managed dataset. You can refresh the connection at any time to get the most up-to-date information.
This avoids the trap of passing around stale spreadsheets, since everyone is connected to the same single source of truth.
Understanding Export Limits and Potential Issues
If you're unable to export data or the option is missing, it's usually due to one of the following reasons:
- Administrator Settings: Your company's Power BI Admin can disable data exports at a tenant level. If no one in your organization can export, this is likely why.
- Report-Specific Settings: A report developer can disable exports of the reports they author for all but a select audience they authorize themselves.
- Row Limits: Power BI enforces limits on exports to maintain performance. By default:
For exports larger than this, Analyze in Excel or Power Automate are ideal alternate strategies.
- Data Permissions: Your level of access to the underlying dataset matters. In general, you need what's known as 'build' permissions to see and make use of the underlying data option for exporting data from most Power BI reports.
Final Thoughts
Moving data out of Power BI is a matter of choosing the tool that best fits your immediate need. For a quick snapshot that mirrors your on-screen visual, a direct export of summarized data is perfect. If you need the granular details for a deeper dive, exporting underlying data or copying from the Data View gets the job done. For a more sustainable reporting workflow, using Analyze in Excel provides a live bridge to your data model, empowering your team without creating disconnected files.
We know that managing reports can sometimes feel like a full-time job of just moving data from A to B. Much of the modern data workflow involves exporting from one system and pasting into another, struggling with export limits, and trying to keep everything up-to-date. At Graphed, we’ve automated that entire process by connecting directly to your marketing and sales data sources. Instead of wrestling with BI tools, you can create real-time dashboards and reports simply by asking for what you need in plain English. If better workflow insights interest you, you should try Graphed for yourself.
Related Articles
How to Enable Data Analysis in Excel
Enable Excel's hidden data analysis tools with our step-by-step guide. Uncover trends, make forecasts, and turn raw numbers into actionable insights today!
What SEO Tools Work with Google Analytics?
Discover which SEO tools integrate seamlessly with Google Analytics to provide a comprehensive view of your site's performance. Optimize your SEO strategy now!
Looker Studio vs Metabase: Which BI Tool Actually Fits Your Team?
Looker Studio and Metabase both help you turn raw data into dashboards, but they take completely different approaches. This guide breaks down where each tool fits, what they are good at, and which one matches your actual workflow.