Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hi team,
I got performance issue after using calcuation group in one of my PBI report.
This PBI report get data directly from a semantic model, it shows some measures by quarterly, yearly, YoY, like following screenshot.
Totally have 37 measures.
If I just show the data by quarterly, there is no any issue, because I don't need to use calculation group, the performance is good, take around 3-4 secs to show the result.(if only with green part header)
But if I add the FY 2022 - FY 2025 or FY22-23 - FY24-25, I have to add the calculation group I created, it will be slow, take more than 20 secs. (green + yellow color header together)
I have a separate table to save the header like Q1'FY22 Actual, Q1'FY25 Current Flash...etc, this table join with fact table, but for FY related value, it can't directly sum up, I have to calculate in calculation group.
Besides this dashboard, my other dashboards performance also affected by calculation group, without calculation group, I need to create so many measures, with calculation group, the performance is not good.
Do you have any suggestion about the performance issue with calculation group? thank you.
This is the logic of this calculaction group item:
Solved! Go to Solution.
Hi @Tracy000 ,
Thank you for reaching out to us on the Microsoft Fabric Community Forum.
As per my understanding you can follow these steps to improve performance:
Avoid applying ALLSELECTED on entire tables. Instead, apply filters only on necessary columns.
Use DAX Studio to analyze query execution time. Identify slow operations (especially FILTER, ALLSELECTED, and CALCULATE).
Create a static table that maps BS_header values to fiscal years. Use this table in relationships instead of extracting values dynamically with LEFT, RIGHT, or CONCATENATE.
If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.
Hi @Tracy000 ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi @Tracy000 ,
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.
Hi @Tracy000 ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hi @Tracy000 ,
Thank you for reaching out to us on the Microsoft Fabric Community Forum.
As per my understanding you can follow these steps to improve performance:
Avoid applying ALLSELECTED on entire tables. Instead, apply filters only on necessary columns.
Use DAX Studio to analyze query execution time. Identify slow operations (especially FILTER, ALLSELECTED, and CALCULATE).
Create a static table that maps BS_header values to fiscal years. Use this table in relationships instead of extracting values dynamically with LEFT, RIGHT, or CONCATENATE.
If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.