Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
Hi all!
I have a table that contains multiple million rows.
Until now I had a simple calculation of sales value * sales price as a calculated column.
Now, what is your oppinion? Makes it more sense to have it as a calulcated column or is it better for a iterator like SUMX?
I feel like in most of the cases, I would use a measure and not a calculated column. I would only say use it as a calculated column if you are having performance issues and it is used in lots of different measures or visualiztions. Or if you needed to output 100k row paginated reports.
But even then, for something simple like that, I would just move the calculated column to power query or within even further upstream in the source. We love using views in our sql over our fact tables exactly for this sort of thing.
If this post was helpful, please kudos or accept the answer as a solution.
~ Anthony Genovese
Need more PBI help? PM me for affordable, dedicated training or consultant recomendations!
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.