dosubot[bot] commented on issue #33839:
URL: https://github.com/apache/superset/issues/33839#issuecomment-2990214229

   <!-- Answer -->
   Thanks for clarifying your version. In 4.1.1, the color scheme for charts in 
a dashboard is locked to the dashboard’s scheme, and the chart’s own color 
scheme control is disabled if a dashboard scheme is set. If changing the 
dashboard scheme doesn’t update the charts, this can be due to stale or 
inconsistent metadata—especially the `map_label_colors` and 
`shared_label_colors` fields. Make sure these fields are present and correctly 
formatted in your dashboard’s metadata (dictionary for `map_label_colors`, list 
of strings for `shared_label_colors`)—otherwise, changes might not propagate as 
expected. Also, ensure your frontend and backend are both running 4.1.1 to 
avoid version mismatch issues. 
   
   A workaround that has helped others: edit the chart, go to advanced 
settings, and remove the `map_label_color` object if it exists—this can unlock 
the color scheme control and let you set the scheme again. More details and 
user reports are here: [issue 
32784](https://github.com/apache/superset/issues/32784) and [discussion 
33678](https://github.com/apache/superset/discussions/33678).
   
   If you’re still stuck, double-check the dashboard metadata and try a full 
browser refresh after changing the dashboard scheme, as the UI in 4.1.1 doesn’t 
always update reactively.
   
   
   <!-- Dosu Comment Footer -->
   *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
   
   ---
   <sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/4ee2d0a5-0375-4d11-8908-f96a3a7f1860?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/4ee2d0a5-0375-4d11-8908-f96a3a7f1860?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/4ee2d0a5-0375-4d11-8908-f96a3a7f1860?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/4ee2d0a5-0375-4d11-8908-f96a3a7f1860?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/4ee2d0a5-0375-4d11-8908-f96a3a7f1860?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/4ee2d0a5-0375-4d11-8908-f96a3a7f1860?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/4ee2d0a5-0375-4d11-8908-f96a3a7f1860?feedback_type=other)</sup>&nbsp;&nbsp;[![Join
 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[!
 [Share on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/33839)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to