Skip to main content

Wrong Totals in Power BI

Yes, you heard it right Power BI still hasn't figured out how to show the correct totals. One of the most common questions in the Power BI community is related to it. So, let's figure out what can you do to correct your totals.

I am using Sample Superstore data to start getting rid of the implicit measures that have already been created. I am creating a matrix with categories and sub-categories. Let's include the total sales, total profit, and the total number of orders received (if you are wondering how these measures are created then it's just the sum of sales, profit, and distinct count of order ID respectively).

Protip- One of the best practices involves creating a separate table for measures (stand-alone table). In this case, we only have 5 measures but what if you have 70-80 measures all in the fact table.

If you critically note the total for sales and quantity sold shows the correct total but if you sum up the total number of orders for furniture it doesn't sum up to 1764. Also, if we look at the total at the end for several orders it is 5009 which exactly matches the distinct count of the order ID.

What's actually going on?? Let's debug this so the total on the matrix is the total where we haven't defined the level on which the calculation needs to be done so by default it shows me the distinct count of order id. There are multiple ways to correct this the most common approach will be using SUMX and values.

Let's see how it works. I am creating another measure using SUMX and Values. We will define the level as a sub-category and the measure will look something like this.


Now let's get back to our matrix. You can see now the total is corrected. But is it the correct number?


With the new measure, you are creating an iterated sum on the level of the subgroup. 1764 in the furniture category shows the distinct count of order IDs and there can be two products in a category with the same order id. Thus, 1764 only shows the distinct order ID associated with a sub-category which is correct while on the other hand, 1984 can include the multiple order ID (can show wrong results). 

If you are using the above method be cautious about the level you want to sum. Another method is not so common but you can create calculated columns(follow the link to learn more about calculated columns). This is something a BI developer doesn't prefer because calculated columns can come up with their own disadvantages.


Thanks for Reading Let's connect on LinkedIn. For more such blogs and pro tips do follow us




Comments

Popular posts from this blog

Ultimate Beginners Guide to DAX Studio

There are zillions of external tools available with Power BI but DAX Studio is one of the most commonly used tools to work with DAX queries. It is a perfect tool to optimize the DAX and the data model. In this blog let's shed some light on the basic functionalities that can take your report to the next level. ARE YOU READY?  To start you will need the latest version of the DAX Studio. You can download it from their website . Don't worry you don't have to pay for the license. Fortunately, DAX Studio is a free tool As a BI Developer, I am using DAX Studio regularly. Based on my experience I use it for several purposes but in this blog, I will highlight the most common ones. Extracting a dump of all the measures used in your PBIX. Why do we need to do this? It can be used for documentation purposes also sometimes we try to reuse the DAX and such a dump comes in handy in this scenario. How to achieve it? Open the DAX Studio it is located under the external tools once you open t

Identify and Delete Unused Columns & Measures

Heavy dashboards and a bad data model is a nightmare for every BI Developer. Heavy dashboards can be slow due to multiple reasons. It is always advised to stick with best practices. Are you still figuring out about those best practices then you should definitely have a quick read on Best Practice Analyser ( link ). One of the most common issues with slow dashboards is unused columns and unused measures.  It is very normal to load some extra columns and create some test measures in your dashboard but as a part of cleanup process those unused columns and unused measures should be removed. Why we are removing them? Because if you keep them then ultimately it will increase the size of your data model which is not a good practice.  How to identify the culprits (unused columns and unused measures)? In today's blog we will provide you with 2 most common external tools which will help you in identifying the culprits. More external tools😒. Who's going to pay for this? To your surprise

Best Practice Analyser (BPA) Guide

Do you want to save tons of efforts to check if your data model and PBIX file follows the standard best practices and norms? Then this blog is for you. If you are a follower of our channel we already deep dive into the importance of the DAX Studio as an external tool. If you are a beginner I would highly recommend to visit this blog . In today's blog we will check how Tabular Editor can help to optimize the data model.  Best Practice Analyser allows to define or import best practices. It will make sure that we do not violate the best practices while developing a dashboard. Isn't it exciting!! Before we start make sure you already have Tabular Editor version 2.24.1 installed on your system. To install it do visit this link and select the link for windows installer. Once Tabular Editor is installed it will reflect in your PBIX file under external tool. Also, we need to define the standard rules. To do so in your advanced scripting or C# script copy this and save it via Ctrl+S. An