This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Hi,
i finished my report and now i am reducing the time using the performance analyzer, i can do the same think using 3 different ways, and i whant to know which is better.
1. Create the calculation as a columns directly in the query when i am importing the data.
2. measures.
3. calculate columns
i create many conditionals formatting for background colors and to reduce the load time i what to use the better way.
so for example for the same conditional.
1. create a column on the database with the HEX code
2. measure1=if(column1=1;"#e6e6e6";"#ffffff")
3. calculatecolumn1=if(column1=1;"#e6e6e6";"#ffffff")
Solved! Go to Solution.
Hi @santiagomur
my opinion and experience:
Create column database in the origin query from data source - the best option, but it will affect on refresh data process
calculate column is the second option
measure will not be effective, emasure useful for all-datasource scope
do not hesitate to kudo useful posts and mark solutions as solution
Hi @santiagomur
my opinion and experience:
Create column database in the origin query from data source - the best option, but it will affect on refresh data process
calculate column is the second option
measure will not be effective, emasure useful for all-datasource scope
do not hesitate to kudo useful posts and mark solutions as solution
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 36 | |
| 33 | |
| 31 | |
| 21 | |
| 16 |
| User | Count |
|---|---|
| 66 | |
| 55 | |
| 31 | |
| 26 | |
| 23 |