How to Remove Sum of in Power BI
Seeing "Sum of" automatically added to your column headers in Power BI is a common experience, especially when you're just starting out. While Power BI is trying to be helpful by summarizing your numeric data, it can make your reports look cluttered or misrepresent data that shouldn't be added together at all. This article will walk you through four simple methods to remove it, from quick visual-specific fixes to permanent changes in your data model.
Why Does Power BI Add "Sum of" in the First Place?
Before we jump into the "how," let's quickly cover the "why." Power BI's intelligence is built around the idea of analyzing and visualizing aggregated data. When you drag a column containing numbers into a visual like a table or a chart, Power BI assumes you want to perform a calculation on it. The default calculation, or summarization, for numbers is almost always a SUM.
This is extremely useful when you're working with metrics like sales, revenue, or quantity. You want to see the total sum, not a long list of every individual sale. However, this becomes a problem when you have numeric columns that aren't meant to be added up, such as:
- Year columns (e.g., 2023, 2024)
- ID numbers (e.g., OrderID, CustomerID)
- Product codes or SKUs that happen to be numbers
- Postal codes
Seeing "Sum of Year" makes no sense and can confuse anyone reading your report. Luckily, you have several ways to control this behavior.
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.
Method 1: The Quick Fix - Using "Don't Summarize" in a Visual
This is the fastest way to solve the problem for a single chart, table, or matrix. If you just need a quick fix for one specific visual and don't want to change the underlying behavior of the field everywhere, this is the tool for the job.
Let's say you've added a 'Product ID' column to a table, and Power BI has awkwardly renamed it "Sum of Product ID."
Here’s how to fix it:
- Select the visual in your report that has the "Sum of" header.
- Look at the Visualizations pane on the right side of the screen. Find the field well containing your column (this will likely be "Values," "Columns," or "Y-axis").
- Locate the field that's being incorrectly summed up (e.g., "Sum of Product ID").
- Click the small downward-facing arrow next to the field name.
- A context menu will appear. The current summarization (likely "Sum") will be selected. Simply choose "Don't summarize" from the list.
Instantly, the title in your visual will revert to its original name (e.g., "Product ID"), and Power BI will show the individual values from that column instead of a single, massive summed number. Problem solved for this specific visual.
When to use this method: You're working on a one-off chart or table and need to show raw values without aggregation, but you might want to sum that same field in other visuals.
Method 2: The Permanent Solution - Changing Default Summarization
Constantly having to change the summarization for the same field every time you create a new visual gets old fast. If you have a column that should never be summarized (like an ID, year, or zip code), you can tell Power BI to stop summing it by default. This change will apply across your entire report, saving you a lot of clicks.
Follow these steps to set the default behavior:
- In the Data pane on the far right, find and select the column you want to modify (e.g., the 'Year' column in your 'Calendar Table').
- When you click the column name, a new contextual tab will appear in the top ribbon called "Column tools." Click on it.
- Look for the "Properties" section in the ribbon. You will see a dropdown field for "Summarization." By default, it will say "Sum" for numeric fields.
- Click this dropdown menu and select "Don't summarize."
That's it! Now, whenever you drag that 'Year' field into a new table, chart, or slicer, Power BI will treat it as a category and won't try to sum it. It will no longer add the "Sum of" prefix.
When to use this method: This is the best practice for any numerical column that serves as an identifier or a category. Set it once and you won't have to think about it again.
Method 3: The Simple Rename - Keep the Sum, Change the Name
Sometimes the problem isn't the summarization itself - you actually want the total - but you just dislike the generic "Sum of [Field Name]" title. For instance, "Total Sales" or simply "Sales" looks much cleaner and more professional than "Sum of SalesAmount."
For this, you can just rename the field directly in the visual without changing any calculations.
There are two ways to do this:
Option A: The Double-Click
- Select your visual.
- In the Visualizations pane, under the appropriate field well ("Values," "Y-axis," etc.), find the field you want to rename.
- Double-click directly on its name.
- The name will become an editable text box. Type in your preferred heading (e.g., "Total Sales") and press Enter.
Option B: The Menu
- Click the small downward-facing arrow next to the field name in the Visualizations pane.
- From the context menu, select "Rename for this visual."
- Type in your new name and press Enter.
The column header in your visual will update immediately, but the underlying data and aggregation (the Sum) remain unchanged. This is purely a cosmetic change for better-looking reports, and just like Method 1, it only applies to the specific visual you are editing.
When to use this method: You need the summary calculation but want a clear, custom title for your chart axis or table column in a specific visual.
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.
Method 4: The BI Pro's Choice - Creating an Explicit DAX Measure
As your skills in Power BI grow, you'll find that relying on its automatic "implicit" measures can be limiting. The most robust, scalable, and professional way to handle calculations is by creating your own "explicit" measures using DAX (Data Analysis Expressions).
This sounds more intimidating than it is. A simple SUM measure is a great first step into the world of DAX.
By creating a measure, you define the calculation and the name in one step. The "Sum of" prefix will never even have a chance to appear.
Here’s how to create a basic measure:
- Right-click on the table that contains the data you want to sum (e.g., your 'Sales' table) in the Data pane.
- Select "New measure."
- The formula bar will appear at the top of the report canvas. You will write your DAX formula here.
- Enter the following formula, replacing
'Sales'[SalesAmount]with your own table and column name: - Press Enter to save the measure.
You'll now see a new item in your 'Sales' table with a calculator icon next to it named "Total Sales." You can now drag this measure into any visual. It will always be named "Total Sales," it will always perform a SUM, and you have a centralized formula that can be easily edited or reused anywhere in your report.
WHEN TO USE THIS METHOD: Creating explicit measures is a core best practice in Power BI. While it seems like more work initially, it makes your reports more maintainable, powerful, and easy to understand in the long run.
Final Thoughts
Power BI's "Sum of" prefix is a classic indicator that you're working with its default summarization feature. Removing it is straightforward once you know your options: you can use the "Don't Summarize" option for a quick fix in one visual, change the default summarization for a permanent site-wide solution, rename the field for a cleaner look, or write a simple DAX measure for ultimate control and scalability.
Spending a few hours setting up these kinds of visualizations, tweaking settings, and wrangling data across different platforms - like Power BI, Google Analytics, Salesforce, and your ad accounts - is exactly the type of manual work that distracts from getting real insights. We built Graphed because we believe there's a faster way. It connects all your data sources and allows you to create dashboards and reports in seconds simply by describing what you want in plain English, allowing you to focus on an answer, not on the tedious process of getting there.
Related Articles
How to Create Facebook Ads API for Claude Code
Create a Meta Marketing API access token that never expires, using a system user, so Claude Code can pull Facebook ad reports and manage campaigns.
ClickHouse vs Postgres: When to Switch to Columnar
Comparing ClickHouse vs PostgreSQL means matching storage architecture to workload. Row storage wins for transactions. Columnar wins for scan-heavy analytics.
Google Ads for Orthodontists: Get More Booked Consults
Most orthodontic Google Ads campaigns waste money on low-intent searches. The problem is structure, not the platform.