Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. 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
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 |
|---|---|
| 44 | |
| 43 | |
| 38 | |
| 18 | |
| 16 |
| User | Count |
|---|---|
| 67 | |
| 63 | |
| 30 | |
| 30 | |
| 23 |