Budget allocation: combining different levels of granularity in Power BI


Budget allocation: combining different levels of granularity in Power BI


Allocating budgets on a different level is not easy to manage in DAX. It was (and still is) a DAX struggle for me.

This blog post will guide you through the different steps I took to easily manage the different granularities (and write easy DAX afterwards) by allocating budget on day level using Power Query.

The problem

I created several sales reports, but in order to get a complete view and gain more insights in the figures, I had to include the budget figures.

The customer provided excel budget files, but these files were created using different aggregation levels. The source files were weekly budgets for department A and monthly budgets for department B. Reporting on the other side required weekly and monthly analysis for both departments.

As you might have noticed, a week can contain dates of multiple months, e.g. Sunday 29 September to Saturday 5 October contains 2 days of September and 5 days from October.

When we look at a month on the other side, we can have problems on both sides of the month. The first week of the month can contain dates from the previous month and the last week of the month can contain dates from the next month.

As we can conclude, budget allocation handling different granularities is inevitable.

The solution

As I like to play with DAX, I started writing different formulas, but never achieved the correct result. The only solution I knew would work was to change my dataset using Power Query. The below steps will provide you an easy way to handle this difference in granularities.

Step overview

  1. Load budget file
  2. Generate calendar on day level
  3. Generate calendar on aggregated level
  4. Determine budget on day level
  5. Generate budget on day level

Let’s dive into the details

1.    Load budget file

Let’s start by loading the budget data into you Power BI model.

Make sure you have at least the following columns:

  • A date reference column: preferably month (YYYYMM) or week (YYYYWW)
  • Value


Example: a monthly budget file


2.    Load Calendar table

Generate a calendar table.

Make sure this table also contains the ‘YYYYMM’ and ‘YYYYWW’ columns.

We only allocated budget to working days, so we added an additional column: ‘IsWorkingDay’ (1= working day, 0 = non working day). You might need to create your own logic for this depending on holidays, weekends,…

= if [IsWeekend] = false and [IsHoliday] = false then 1 else 0

3.    Generate a Calendar table on aggregated level

Using the calendar table generated before, we now create an aggregated table to determine the number of working days by month or by week (depending on the use case). We needed both so generated 2 additional tables, one by month and another one by week.


To achieve this, right click the calendar table and choose ‘reference’.

Next use the ‘group by’ functionality and group by YYYYMM or YYYYWW and as aggregation add: SUM(IsWorkingday) as NumberOfWorkingDaysInMonth/Week

The YYYYMM or YYYYWW column is required to link the budget table with the aggregated calendar table.

This will generate a 2 columns table, one indicating the month or week, and another the number of working days in that period.

4.    Determine budget per day

To determine the budget per day, we merge the budget table with the aggregated calendar table.

To add columns for the merged table, simply click the expand icon and select the column to add.


After this merge we now have the following columns

  • Month (YYYYMM) or Week (YYYYWW)
  • Value
  • NumberOfWorkingDaysInMonth/Week

To get the DayValue we simply add a custom column.

After calculating the DayValue, you can remove the Value column (or rename it to “MonthValue” or “WeekValue”), so the distinction is clear for the report designer.

5.    Generate budget table per day

As a final step in preparing our data, we merge the budget table with the calendar table (the one on day level). This allows generating one line for each calendar day.

We merge this on the YYYYMM or YYYYWW column.

When expanding the calendar table, only adding the Date or DateKey (YYYYMMDD) column is enough.

As you don’t need the aggregated Calendar by month table, you can disable load for this table.


Now your budget table is available on day level and easy to create the required DAX measures to generate the correct calculation.

Notice when writing DAX formulas you only sum the DayValues on working days.

= CALCULATE(SUM(Budget[DayValue]); Calendar[IsWorkingDay] = 1)


As a workaround you can create a calculated column so a DayValue is only available on working days.

= IF(RELATED(Calendar[IsWorkingday]) = 1; Budget[DayValue])



Group of computer programmers working in the office. Focus is on blond woman showing something to her colleague on PC.
Updating your Azure SQL server OAuth2 credentials in Power BI via PowerShell for automation purposes
The better way to update OAuth2 credentials in Power BI is by automating the process of updating Azure SQL Server...
Under (memory) pressure
A few weeks ago, a client asked me if they were experiencing memory pressure and how they could monitor it...
Managing files from other devices in a Fabric Lakehouse using the Python Azure SDK
In this blogpost, you’ll see how to manage files in OneLake programmatically using the Python Azure SDK. Very little coding...
Database specific security in SQL Server
There are many different ways to secure your database. In this blog post we will give most of them a...
SQL Server security made easy on the server level
In this blog, we’re going to look at the options we have for server level security. In SQL Server we...
Microsoft SQL Server history
Since its inception in 1989, Microsoft SQL Server is a critical component of many organizations' data infrastructure. As data has...