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!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
We have multiple functions but the question is how to identify if it is table or column or best to use in Measure
Hi,
Unfortunately there isn't a single answer and instead the answer depends on the context. Calculated table, column and measures all have their benefits. Additionally you might consider doign some of the calculation in Powerquery or even at the data base level.
Here are some general pointers: If you can't do the calculations in PQ or at database level I recommend using measures whenever it is possible. They are more efficient than using columns or tables. For tables I would use them for example to create a calendar table or to place some slicer values, but when it comes to calculations I often place calculated tables inside measure variables. Finally for columns, the most often use case is for creating categories or slicers.
Here is a great articley by SQLBI related to this topic: https://www.sqlbi.com/articles/calculated-columns-and-measures-in-dax/
I hope this post helps to solve your issue and if it does consider accepting it as a solution and giving the post a thumbs up!
My LinkedIn: https://www.linkedin.com/in/n%C3%A4ttiahov-00001/
Proud to be a Super User!
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.
User | Count |
---|---|
10 | |
7 | |
5 | |
4 | |
3 |
User | Count |
---|---|
12 | |
12 | |
10 | |
9 | |
9 |