Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Reply
Xriz
Advocate I
Advocate I

SSAS - Dimension does not aggregate in Power BI Desktop

Hello Community,

 

i've got a problem with dimensional aggregation using a tabular model in SSAS. I have a star-schema, where fact is linked to serveral dimensions. The lowest level of time is Month ( linked to DIM via Month_ID). Now when calculating the sum for costs in several years the timedimension is not aggregating for example years. PBI doubles years for any month in filtercontext:

image.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 I never experienced something like that with other models of SSAS tabular. When searching the cube in SSMS AS and do the same query, it is aggregating years. Any suggestions?

 

Edit: I think any aggregation of dimensional values in this model behave this way...

 

SQL Analysis Server 13.0.5026.0

model level of compatibility: 1200

1 ACCEPTED SOLUTION

Hello @v-juanli-msft ,

 

the measure is defined by DAX (sum) in SSAS but its not the problem here. In the meantime I got a solution. The problem was the set sorting of Month and Year. It was sorted by day_ID, which meant that although the day is not on the report, each item is still calculated separately by day. I have now arranged the sort on the basis of fields of the same level, which solved the problem.

 

Nevertheless thanks for your will to help

View solution in original post

2 REPLIES 2
v-juanli-msft
Community Support
Community Support

Hi @Xriz 

Is the "sum_CO_IST" measure created in Power BI or in SSAS?

How do you define it with DAX or MDX?

 

Best Regards

Maggie

Hello @v-juanli-msft ,

 

the measure is defined by DAX (sum) in SSAS but its not the problem here. In the meantime I got a solution. The problem was the set sorting of Month and Year. It was sorted by day_ID, which meant that although the day is not on the report, each item is still calculated separately by day. I have now arranged the sort on the basis of fields of the same level, which solved the problem.

 

Nevertheless thanks for your will to help

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.

Jan25PBI_Carousel

Power BI Monthly Update - January 2025

Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.

Jan NL Carousel

Fabric Community Update - January 2025

Find out what's new and trending in the Fabric community.