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

Shape the future of the Fabric Community! Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions. Take survey.

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
November Carousel

Fabric Community Update - November 2024

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

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.