We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
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!
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 12 | |
| 10 | |
| 10 | |
| 6 | |
| 5 |