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!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live 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
The Power BI Data Visualization World Championships is back! It's time to submit your entry.
| User | Count |
|---|---|
| 52 | |
| 40 | |
| 31 | |
| 24 | |
| 22 |
| User | Count |
|---|---|
| 133 | |
| 118 | |
| 56 | |
| 43 | |
| 43 |