Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get inspired! Check out the entries from the Power BI DataViz World Championships preliminary rounds and give kudos to your favorites. View the vizzies.

Combo chart - when setting column color conditional formatting, the legend shows the wrong color

When using a combo chart, I tried to apply a conditional color to the bars. This works fine and the bars appear colored correctly. However, the legend then shows the wrong color (in this case blue, the first color in the Power BI theme color palette.) This makes it really confusing for the user since the legend shows a color that's not even on the chart.

 

In the first screenshot, I manually set the column color to yellow, prior to enabling conditional formatting:

Combo chart Legend color switches to blue after conditional formatting #1.png

 

Then I apply conditional formatting with a rule. The bars are now the correct color, but the legend color defaults back to blue (first color in color palette):

Combo chart Legend color switches to blue after conditional formatting #2.png

 

PBIX link: https://drive.google.com/file/d/1orauvk1BXefZpKmWp_0KWzvPmJama8Nj/view?usp=sharing

Status: Investigating

Hi @NarWind ,

 

Based on the above information, this issue may need to be addressed further. Since community support engineers don't have that access, I would suggest opening a Support Ticket. If you are a Power BI Pro or Fabric licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you. 
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

 

The link of Power BI Support: Support | Microsoft Power BI

For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community

 

Best Regards,
Zhu

Comments
v-linhuizh-msft
Community Support
Status changed to: Investigating

Hi @NarWind ,

 

Based on the above information, this issue may need to be addressed further. Since community support engineers don't have that access, I would suggest opening a Support Ticket. If you are a Power BI Pro or Fabric licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you. 
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

 

The link of Power BI Support: Support | Microsoft Power BI

For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community

 

Best Regards,
Zhu

NarWind
Advocate I
Hi @v-linhuizh-msft - thank you for the reply. Is this a new process? In the past I have posted Power BI bugs on this forum and your team was able to pass them on to the product team. For example, this one from a few months ago: https://community.fabric.microsoft.com/t5/Issues/Combo-chart-area-below-line-transparency-not-workin...
v-linhuizh-msft
Community Support

Hi @NarWind ,

 

The process has indeed been updated recently. You can create a support ticket, and a Microsoft engineer will directly address your issue. We encourage you to share your experience and solution in the community after your issue is resolved to help others facing similar problems.

 

Best Regards,
Zhu

NarWind
Advocate I
Thanks @v-linhuizh-msft. I tried to create a support ticket since I have a Pro License by going to the Help pane in app.powerbi.com. Then when I try to create the ticket, I have to select a Support Plan which I do not have. The link you gave above for "How do create a support ticket in Power BI" shows outdated screenshots. Is there anyway to create the support ticket without the Support Plan?
NarWind
Advocate I
Following up, after submitting a support ticket with Microsoft, the product team confirmed this behavior is by design and there's no current plan to alter it.
NarWind
Advocate I
Following up, after submitting a support ticket with Microsoft, the product team confirmed this behavior is by design and there's no current plan to alter it.