The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
There are matrix table visual need to apply the color code to the data table.
From the figure show the different performance duration with and without apply color code conditioning formatting.
It is have any suggestion to reduce the performance duration at the same time apply the color code conditioning formatting.
Thanks for help on this.
There are a few ways to improve performance of visuals with color conditioning formatting:
Limit the amount of data displayed in the visual by using filters or slicers. This will reduce the amount of data that needs to be processed, and can improve overall performance.
Consider using a different visual that doesn't require color conditioning formatting, such as a table or a chart.
Try simplifying the color conditioning formatting by using fewer colors or applying the formatting to a smaller subset of data. This can reduce the amount of processing required for the visual.
Reduce the number of conditional formatting rules in the visual. Each rule adds additional processing time, so limiting the number of rules can improve performance.
Consider upgrading your hardware or using a faster internet connection if possible, as this can also help improve performance.
Conditional formatting is just another value for the visual to render then apply, so the performance of it will depend on the DAX you have written in your base measures to determine how to return the values. And it depends on how you are telling it to render the format too - using another measure, using a range of numbers, or using a fixed color metric.
We will need a lot more info to assist.
How to get good help fast. Help us help you.
How To Ask A Technical Question If you Really Want An Answer
How to Get Your Question Answered Quickly - Give us a good and concise explanation
How to provide sample data in the Power BI Forum - Provide data in a table format per the link, or share an Excel/CSV file via OneDrive, Dropbox, etc.. Provide expected output using a screenshot of Excel or other image. Do not provide a screenshot of the source data. I cannot paste an image into Power BI tables.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingThanks @edhans
This is the color measure that applied to the PBI report as local measure.Is there a difference in term of performance between local and SSAS measure since this measure added as a local.
_Sample =
Var Sales1 = [Adv_Sales (% TN v TTL)]
Var Sales2 =
CALCULATE([Adv_Sales (% TN v TTL)],
ALL('STATE'), ALL('SALES_CENTER'), ALL('PRODUCT')
)
Return
IF(Sales1 > Sales2, "GREEN", "RED")
There is no difference assuming it isn't a composite model. If it is a thin report (Live connection) it will be the same.
The key then is what is the [Adv_Sales (% TN v TTL)] measure? That has to be calculated twice, once within the filter context of the report, and then with the filters removed from 3 tables.
And that is 1 time per "Cell". So a 12 month bar chart is 12 times. A matrix with 4 columns and 30 rows is 120 times. The engine greatly optimizes this and takes advantage of the cache, but of that measure is slow, then the conditional formatting will be doubly slow.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingThanks @edhans
The [Adv_Sales (% TN v TTL)] - This measure taking 15 seconds to populate the data.Can you help to redefine this measure.
15 seconds is an extraordinarily long time. That is the measure you need to optimize before trying to optimize conditional formatting that references that measure twice, once with and once without certian filters removed. The one with filters removed could take considerably more time if it has to process more of the fact table.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingUser | Count |
---|---|
35 | |
14 | |
12 | |
11 | |
8 |
User | Count |
---|---|
44 | |
43 | |
19 | |
18 | |
17 |