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,
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
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.
| User | Count |
|---|---|
| 28 | |
| 23 | |
| 18 | |
| 18 | |
| 15 |
| User | Count |
|---|---|
| 49 | |
| 44 | |
| 42 | |
| 39 | |
| 32 |