This issue I've originally found in Winter 17 seems not fixed in Winter 18 release. However the issue does not affect Report Charts based on Opportunity.StageName - but on Custom Objects it's perfectly reproducible.

Original Question

Colors have crucial meanings in processes, e.g. lost- or bad things must be drawn more red alike in contrast to won- or good things which are expected to take shades of green. There is practically no room for discussion with users and clients on this point. There is a high risk of bad business decisions made on wrong colors in charts, because the information can be misleading and the processes become error prone.

I have defined custom colors for pick-list values like this

enter image description here

Hint: In this particular example I have to use gray for "Lost" an need a gradient from pink to green on the status progression. But my issue is of general nature.

Now in Aloha the chart is taking these colors perfectly as expected and shown here:

enter image description here

But now in lightning I've tried the same by putting the exact same report as Report Charts on the homepage. Unfortunately, this component ignores the color setting and draws it's own automatically assigned colors over my carefully selected manual color definition. It looks like this:

enter image description here

The fact that Lost becomes green is absolutely not acceptable for my use case.

Now I also tried it with Dashboards, but again without luck and the color mess is basically the same:

enter image description here

Strangely, if you go to reports and open up the report in LEX, the chart is drawn using the correct color definitions (as expected and as everywhere in Aloha)

enter image description here


  • Is there a way to make the new Lightning Dashboards or any Report- or Chart- component use my manual color definition?
  • Is there any other option to enforce colors in an other way on any Lightning Chart without coding my own charting components for that?
  • Is this simply a missing feature in LEX? If so: is it one the roadmap to be improved? Any safeharbor-timeline? I ask, because I need to make a decision whether to take care of the drawing myself an write my own charting compo or if waiting is an option. I would clearly prefer a Standard solution without 3rd party stuff or own implementations.

Appendix 1

If you use many Report Chart Components on one single Flexipage, the automatic coloring is calculated per each Component separately, which makes the whole situation even worse: on one chart Status=Calculation is rendered brown on another blue and on the last in cyan. This is a total mess-up and no one will make any sense out of it:

enter image description here

Appendix 2

The color assignment is the same in LEX setup than it is in Aloha setup (reviewed as crmprodev suggestet)

enter image description here

Appendix 3

I found that this issue at least does not exist for Standard Opportunity StageName. Report-Charts based on that field, will get their colors perfectly rendered in LEX:

enter image description here

However this seems to be an ongoing flaw on custom objects, possibly on custom picklists on standard objects or other standard fields might be affected, too.

  • 1
    Looks like you have found an area which Salesforce missed to care. Now this is a bug. I think bug tag should be added to the question.
    – Ashwani
    Jan 21, 2017 at 15:07
  • 1
    @Ashwani as you suggested I added the bug-tag. If anyone feels that this is not a bug but something else: please feel free to remove that tag again.
    – Uwe Heim
    Jan 21, 2017 at 15:10
  • 4
    I never understood the importance of color to users until in the med field we changed the color on the packaging of our products and nurses started using wrong products despite clear labels. Issue, they used "the green one" and had no other association other than color. But I digress. Hope you get this on the squash list
    – Eric
    Jan 21, 2017 at 16:30
  • 2
    @Eric sure thing: colors are crucial. It's a brain thing. Human brains operate in the following order of processing: 1. movement, 2. color, 3. text/glyphs. So color-information will always trump labels (at least one of my professors told me so some years ago)
    – Uwe Heim
    Jan 21, 2017 at 16:47
  • 1
    This issue still exists in Winter 18. Now hoping for Spring 18.
    – Uwe Heim
    Oct 27, 2017 at 14:19

1 Answer 1


I was very happy to see, that in Spring 18 this issue seems to be resolved by Salesforce. There was no need to change anything on my end - it just works now on any Orgs I've checked so far - and looks awesome!

enter image description here

Thanks Salesforce for fixing this!

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .