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!Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Hi,
I'm trying the use the information given as the result of a calculation through a measure or calculated column to feed back into a dimension table, is there any smart way / best practice to do so?
I have a model where I'm retrieving information from different fact tables to make calculations.
1 table with facts (actuals)
1 table with budget (coming from a complete different data source than the actuals).
Based on my actual table, I could generate a product dimension table that actuals, budget (and other fact tables) connect to.
In order to get an actual vs budget, I created a measure, which is fine.
Now that I have a variance to budget calculated, what is the best way to categorise products being over budget as "over budget" and import this information back into my dimension table?
The best way I could find was doing some some of loop / redondance in the model:
1- create a second actual table, where each product exists only once a month, and use my measures of actuals and budget as calculated columns, so I can get the variance as a calculated column.
2- Then, for each row, I apply a simple if variance to budget < 0 then "over budget" otherwise "ok".
3- Finally, in my dimension table, I'm taking the last known result of the over budget category calculation.
This allows me to have the attribute in my dimension table, but I loose track of the historical information, as I'm only taking the latest known result to categorise a product as being over budget.
Another option is instead of step 3 above, I use the information straight out of the fact table... which means I end up with separate fact tables structured in a different way, which seems counterintuitive.
In the current state my model works, I'm just thiking if there's a smarter way to compute an result back into the model, or a "best practice" I could follow.
Thanks!
hi @Anonymous
First, you should know that:
1. Calculation column/table not support dynamic changed based on filter or slicer.
2. Measure can be affected by filter/slicer, so you can use it to get dynamic summary result in a visual by its row context.
https://www.sqlbi.com/articles/calculated-columns-and-measures-in-dax/
So you could not drag a measure into x-axis.
Second, for your requirement, you could create a dynamic segmentation in Power BI
https://powerbi.tips/2016/04/power-bi-histogram-with-bins/
http://tinylizard.com/segmentation-power-bi/
Regards,
Lin
You simply cannot do that. Measures are by definition one-way streets. Meaning they are truly dynamic and you can't store a measure result anywhere.
Once you start with a measure you need to do anything depending on it as measures too.
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!