- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

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:
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

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
Join us at the Microsoft Fabric Community Conference
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Power BI Monthly Update - February 2025
Check out the February 2025 Power BI update to learn about new features.

Subject | Author | Posted | |
---|---|---|---|
Anonymous
| 06-25-2024 01:32 AM | ||
09-19-2023 01:35 AM | |||
07-25-2023 02:20 PM | |||
06-21-2023 12:37 AM | |||
05-08-2024 11:12 AM |
User | Count |
---|---|
87 | |
81 | |
53 | |
37 | |
35 |