Why is Power BI Not Showing All Data?

It’s one of the most frustrating experiences for any Power BI user: you’ve connected your data, built your report, and yet the final numbers just don’t seem right. You know there should be more data, but for some reason, your visuals are coming up short. This article breaks down the common reasons why Power BI might not be showing all your data and gives you a step-by-step checklist to find and fix the problem.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Don't Panic: Start with the Simple Checks

Before you dive into complex query settings, always start with the most obvious culprits. It's surprising how often the solution is right on the surface.

• The Refresh Button: It sounds basic, but did you actually refresh your dataset? If you're working in Power BI Desktop with an imported data source (like an Excel file or CSV), it won't automatically update from a live data source. Hit the "Refresh" button on the Home ribbon to pull in the latest data.
• Slicers and Filters: Check the Filters pane on the right side of your report view. Power BI has filters at three levels: filters on a specific visual, filters on the entire page, and filters on the entire report. It's easy to set a filter for one chart and forget it’s impacting everything on the page or report.

Go to the Source: Investigate Your Data Connection

If the simple checks don’t solve it, your next stop is the data source connection itself. How Power BI gets the data can sometimes be the reason you're not seeing everything.

DirectQuery vs. Import Mode

Power BI offers two primary ways to connect to data sources, and they behave very differently:

• Import Mode: Power BI takes a full copy of your data and stores it within the .PBIX file. This is fast for analysis but means you're looking at a snapshot from the last refresh. If data is "missing," it could be because the last scheduled refresh failed or hasn't run yet.
• DirectQuery Mode: Power BI connects directly to the source database and runs live queries every time you interact with a visual. While this gives you real-time data, it also makes you subject to the source database's rules and performance. Some data sources have a built-in limit on the number of rows a query can return (often one million) to avoid overloading the system. If you’re working with a massive dataset, Power BI may simply be showing a truncated result.

Permissions and Access

Are you certain the credentials used to connect to the source have full access? If your account connects to a database view that only shows data for the "North America" region, you will never see sales from "Europe," no matter what you do in Power BI. Verify that the account used in Power BI’s data source settings has the same level of access as you do when you view the data directly in the source platform (like Salesforce or a SQL database).

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

The Main Suspect: A Deep Dive into Power Query

More often than not, the culprit is hiding within the Power Query Editor - the engine room where you clean and transform your data before it even reaches the data model. Every action you take here is recorded as an "Applied Step," and a single misplaced step can filter out thousands of rows.

To get here, click on "Transform data" from the Home ribbon.

Follow the Trail: Your "Applied Steps" are Clues

On the right side of the Power Query Editor is a list of “Applied Steps.” Power BI automatically adds some of these, like "Promoted Headers" and "Changed Type." This is your troubleshooting audit log. Click on each step, starting from the top, and watch the data in the preview window. As you go down the list, you can pinpoint the exact step where your rows suddenly disappear.

Invisible Filters You Forgot About

This is extremely common. You may have filtered a column to check a value and forgotten to remove the filter. Look for the small filter icon next to any column header. For example, you might have filtered a "Status" column to only show "Completed" deals while building the report, inadvertently hiding all "In Progress" or "Lost" deals from your final analysis.

Beware of "Remove Errors"

The "Remove Errors" function is a powerful tool for cleaning messy data, but it can also be a hidden data trap. Imagine a Sales Amount column that is mostly numbers, but a few rows contain text like "N/A" or were entered with a typo. If you change that column's data type to "Decimal Number," those text entries will become errors. If a later step in your "Applied Steps" removes all errors, you've just deleted those rows from your dataset without realizing it.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

When Merges and Joins Go Wrong

When you combine tables using the "Merge Queries" feature, the type of join you use is critical. Power BI defaults to a "Left Outer" join, but if you switch it to an "Inner" join, you might lose data unexpectedly.

• Inner Join: This join type will only keep rows where a matching key exists in both tables. If you are joining a Sales table to a Product Details table on ProductID, but some sales have a new ProductID not yet logged in your Product Details table, an inner join will drop those sales rows completely.
• Left Outer Join: This will keep all rows from the first (left) table and bring in matching data from the second (right) table where it exists. If there's no match, the columns from the right table will just be blank (null), but you won't lose your original sales rows.

Always double-check your join type to ensure it aligns with your goal. If you want insight into all sales, a Left Outer join from Sales to Product Details is almost always the right choice.

Checking the Front End: Data Model & Report Filters

If you've cleared Power Query and you’re still seeing discrepancies, the issue may be in your data model, DAX calculations, or the report canvas itself.

Data Model Relationships

How your tables are related in the "Model" view dictates how filters flow between them. A relationship might be inactive or filtering in the wrong direction.

An arrow on the line connecting two tables shows the filter direction. If you have Customers -> Sales, filtering a slicer by a customer will filter the sales table. But filtering by a sales attribute won't necessarily filter the customer table unless you enable a "bi-directional" relationship. An incorrect relationship structure can cause visuals that combine fields from multiple tables to show incorrect or incomplete results.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

When DAX Gives You Less Than You Expect

Your Data Analysis Expressions (DAX) measures can contain their own hidden filters. The most common function here is CALCULATE. For example, let's say you write a measure to isolate sales from a specific region:

North Region Sales = 
CALCULATE(
    SUM(Sales[SalesAmount]),
    Sales[Region] = "North"
)

If you use this measure in a card or chart, it will only show sales for the North region, regardless of what other slicers or filters you apply to the report. If you’ve inherited a report from a colleague, check the DAX formulas of your measures to see if they contain hard-coded filters that are overriding your selections.

Discrepancies Between Desktop and Power BI Service

Sometimes, a report works perfectly on your PC (Power BI Desktop) but shows incomplete data when published to the Power BI Service (the cloud version).

• Scheduled Refresh Errors: The most common problem. In the Power BI Service, go to the workspace, find your dataset, and check the "Refresh history." It will tell you if the recent scheduled refreshes have succeeded or failed. A failure could be due to expired data source credentials, changes in the source data schema, or server issues.
• Data Gateway Issues: If your data source is on-premise (e.g., a local SQL server), you need an on-premise data gateway to securely push that data to the Power BI Service. If the gateway is down, not configured correctly, or needs an update, your refreshes will fail and your online report won't show the latest data.

Final Thoughts

Finding missing data in Power BI is a process of elimination that involves checking every stage of the data journey. By systematically investigating your source connections, Power Query steps, report filters, and data model relationships, you can almost always track down the cause and get your numbers to align with reality.

We know this process can be incredibly time-consuming and technical. Manually combing through query steps, DAX measures, and relationship diagrams is exactly the kind of friction that keeps teams from getting timely access to their business insights. It’s why we built Graphed. We connect directly to your marketing and sales platforms and let you build real-time dashboards using simple, natural language. Instead of hunting for a broken filter, you can just ask, "Show me my campaign revenue from Shopify versus Facebook Ads spend for this month," and instantly get the answer you need.