How to Remove Count of Values in Power BI

It’s one of the most common frustrations when you're starting with Power BI: you drag a field into a table or chart, and it immediately turns into a "Count" instead of showing the individual values you wanted. This article will walk you through exactly why this happens and show you several ways to fix it, from a quick click to a more permanent solution.

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

Why Power BI Defaults to "Count"

Before diving into the fixes, it helps to understand why Power BI does this in the first place. Power BI is a data aggregation tool at its core. Its main job is to summarize large datasets into understandable insights. This process is called summarization or aggregation.

Here’s how it generally makes its decisions:

• For columns with numbers: If Power BI sees a column of numbers (like sales amounts or quantities), it assumes you want to perform a calculation. Its default action is usually to Sum them.
• For columns with text or non-numeric data: If the column contains text (like names, categories, or IDs), Power BI knows it can't add them up. The next best way to summarize them is to Count how many there are.

This "Count of Values" issue typically happens with fields that serve as identifiers, such as Product SKUs, Order IDs, Customer Names, or geographical locations. You don't want to add or average these, you simply want to see the list. Fortunately, telling Power BI your intention is straightforward.

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

Solution 1: The Quick Fix with "Don't Summarize"

The fastest way to stop a visual from counting your values is to change the setting directly on that specific visual. This is perfect for one-off tables or charts where you need to display raw data.

Let's use an example. Imagine you have a dataset with customer names and you want to create a simple table showing them.

1. Create a new 'Table' visual on your report canvas.
2. Drag the 'Customer Name' field from your 'Fields' pane into the 'Columns' box in the 'Visualizations' pane.
3. You'll notice that instead of a list of names, the table just shows one number: the total count of all customer names.

To fix this:

• In the 'Visualizations' pane, under the 'Columns' well, you will see your field listed as "Count of Customer Name."
• Step 1: Click the small downward-facing arrow next to the field name.
• Step 2: A contextual menu will appear. The current selection will be 'Count'. Change this by selecting 'Don't summarize' at the top of the list.

Instantly, your table will update to show each individual customer name, just as you intended. This method is simple and effective, but you'll have to repeat it for every new visual where you use this field.

Solution 2: The Permanent Fix in Column Tools

If you have fields that you never want to be summarized — like IDs, SKUs, or reference numbers — having to select "Don't Summarize" every single time gets old fast. You can set the default behavior for a column so that it never tries to count automatically again.

This is the preferred method for any text-based unique identifier.

How to Set the Default Summarization

1. Select the Column: Go to the 'Data' view or 'Model' view on the left-hand side of Power BI. You can also do this from the 'Report' view. Find your data table in the 'Data' pane and click on the specific column (e.g., 'Product SKU').
2. Open Column Tools: When you select the column, a new contextual tab called 'Column tools' will appear at the top in the ribbon menu.
3. Change Summarization Setting: In the 'Column tools' ribbon, look for the 'Properties' section. You'll find a box labeled 'Summarization'. It will likely say 'Count' or 'Default'.

• Click the dropdown and select 'Don't summarize'.

That's it! Now, any time you drag this 'Product SKU' field into a new visual, Power BI will know to show the individual values by default, without counting or summing them. Note that this change won't affect any existing visuals, you'll still need to update those manually if you've already made them.

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

Solution 3: Checking and Changing the Data Type

Sometimes, the problem isn't just a summarization setting, it's that Power BI misunderstood what kind of data is in your column. This happens frequently when numerical columns are accidentally formatted as text.

For instance, let's say you have a 'Year' column in your data. It contains values like 2022, 2023, 2024. If Power BI imported this as a 'Text' data type, its only aggregation option is to 'Count' the entries. If it were a 'Whole number' type, it would try to 'Sum' them (which is also wrong — you don't add years together!).

Correcting the data type is a fundamental step and can prevent many summarization headaches.

How to Change a Data Type in Power Query

1. Open Power Query Editor: On the 'Home' tab of the main Power BI window, click 'Transform data'. This opens the Power Query Editor, where all data cleaning and prep should happen.
2. Find Your Column: In the Power Query window, find the table and column you need to fix.
3. Check the Type: Look at the icon next to the column header.
4. Change the Type: If the data type is wrong, click on the icon itself and select the correct format from the dropdown menu (e.g., change 'Text' to 'Whole Number'). You can also use the 'Data Type' dropdown menu in the 'Transform' tab.
5. Close & Apply: Once you've made your changes, click the 'Close & Apply' button on the 'Home' tab in Power Query to save your changes and return to the main Power BI report.

Setting the correct data types from the start is a best practice that ensures Power BI handles your fields appropriately and opens up the correct calculation options.

Best Practices and Final Tips

Text IDs vs. Numeric IDs

Even if an ID or code (like a Zip Code or Product ID) is composed solely of numbers, it's often best practice to keep its data type as 'Text'. Why? Because you will never perform mathematical calculations on them. You don't sum Zip Codes or average Employee IDs. Keeping them as text stops Power BI from trying to sum them up by default, and you can more easily manage the "Don't Summarize" setting.

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

Implicit vs. Explicit Measures

Relying on Power BI's automatic summarization is known as using an implicit measure. For advanced reports, analysts prefer creating explicit measures using DAX (Data Analysis Expressions). For example, instead of letting Power BI 'Count' employees, you'd create a measure like:

Employee Count = DISTINCTCOUNT(Employees[EmployeeID])

This gives you full control, the calculation is reusable throughout your report, and it makes your model's logic clearer to others. While it's a more advanced topic, a DAX approach fundamentally solves the auto-summarization problem by giving you complete authority over calculations.

Final Thoughts

Fighting with Power BI's automatic "Count of" summarization is a rite of passage for many users, but stopping it is easy once you know where to look. By either toggling 'Don't Summarize' directly on a visual, setting the column's default behavior permanently, or correcting its underlying data type, you can make Power BI display your data exactly how you need it.

Ultimately, these settings are required because traditional BI tools need you to explicitly define how your data should be handled every step of the way. When building Graphed, we focused on eliminating that friction. You don't have to hunt for settings or change data types, you use natural language to tell it what you want. Asking "show me revenue by product SKU for last month" naturally results in a list of SKUs and their revenue, because the AI understands your intent is to list, not to count. It streamlines the whole process so you get to the insights without getting stuck on formatting hurdles.