Dashboard overrides Chart color schema selected

[marianysilva]

Hello everyone, I’m working with some visualizations in Superset and I’d like to share an issue I’m facing.

My client wants the charts to have specific colors, changing only one filter (type = day and type = night). As a result, I have two charts that use the same metrics but have different where clauses and color schemes.

When I add the charts to the dashboard, the colors aren’t respected, even when I don’t select a color scheme in the dashboard. Additionally, the same metrics are displayed with the same color across both charts.

To achieve what my client asked for, I had to duplicate the metrics with different names and declare the colors in the dashboard’s JSON, forcing it to behave as desired, but this is far from ideal. Do you have any other approaches in mind?

Is there a way to ensure that the colors originally chosen in the chart are respected within the dashboard?

Could we have something more configurable at the chart level inside the dashboard?

Example:

[dosubot[bot]]

To ensure that the colors originally chosen in Superset charts are respected within the dashboard, avoid selecting a color palette in the ColorSchemeControlWrapper. The color scheme defined in the chart's JSON metadata will take precedence over any selected color palette. Therefore, if you do not select a new color palette, the original colors chosen in the charts should be respected ^[1].

Additionally, you can use the label_colors property in the dashboard JSON metadata to specify colors for each metric or dimension. This can help maintain consistency across charts without duplicating metrics. Here's how you can do it:

1. Go to Edit dashboard.
2. Click on the three dots in the top right corner and select Edit properties.
3. Expand the ADVANCED section and find the JSON METADATA field.
4. Add a label_colors section to specify colors for each metric.

Example:

{
  "label_colors": {
    "metric_1": ["#FF0000", "#00FF00"],
    "metric_2": ["#0000FF", "#FFFF00"]
  }
}

This approach allows you to define specific colors for each chart without duplicating metrics ^[2].

To continue talking to Dosu, mention @dosu.

[marianysilva]

#25623

[giftig]

I added a bit of analysis to the slack thread, the code is a bit convoluted around colour maps here but I suspect this could be implemented with a change to the structure of forcedColors in CategoricalColorNamespace / CategoricalColorScale. The getColor method of the latter already has sliceId as context.

Maybe that will help someone have a go at implementing this (I may give it a go if I have some spare time).

[giftig]

I had a bit of a go at this but it looks like it'll require more structural changes than I first thought: giftig@186f7ac

I've managed to have the CategoricalColorScale save the chart-specific forced colours and provide it when getColor is called, but from my logging, near as I can tell, getColor... isn't actually called here. It also has a getColorMap method: giftig@186f7ac#diff-5c8f07b848f506ff247711e59739b51bc93e404ba9afe4993b63b71a918da6b0L229 which provides a flat colour map irrespective of charts, and I suspect that's probably what's being used.

That means it'd probably require several more structural changes to accomplish this and may need a SIP to decide the best way to go about that.