Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Suggest an Idea

Announcements
This page is no longer in use. To suggest an idea, please visit Browse and Suggest.

Consistent colours across a dashboard

BradMazurek
Contributor II
Contributor II

Consistent colours across a dashboard

When we're looking for patterns, colour is a common way of scanning and identifying patterns.

If I'm looking at a dashboard and see a colour that has been associated with a particular field value, I should expect to see the same colour used across all other visualizations that are organized by the same field.

For (a rather contrived) example, if I am looking at count of transactions, average transaction size and sum of all transactions each broken down by region all in pie charts, then the East region should be the same colour in each visualization.

Further, if I had a pie chart for one graph by sales manager and another graph showing sales managers over time, then Bob should be the same colour in both.

Tags (2)
5 Comments
John_Teichman
Former Employee
Former Employee

This capability is already available. Please refer to the documentation for more information.

https://help.qlik.com/en-US/sense/November2019/Subsystems/Hub/Content/Sense_Hub/Colors/assigning-col...

Status changed to: Closed - Already Available
BradMazurek
Contributor II
Contributor II

Hi @John_Teichman, I do not believe the documentation you point to describes the functionality I requested. 

I understand the value of assigning a colour to particular Field Values and that this functionality already exists. If I am doing analysis on support for American political parties, the value of assigning red to the Republicans and blue to Democrats is obvious.

The key to what I am requesting is that the colours be consistent across visualizations irrespective of the user's action. Yes, the user should be able to assign particular colours to values if they have meaning, but the consistency should remain across visualizations regardless.

This should be done by default for two reasons:

  1. As a user, I will often not care what colour is assigned to a Dimension. If I am colouring "Type of Moth" it is unlikely that I care what colour denotes species X versus species Y, but species X should be the same colour across all visualizations.

  2. As a user, if I have 400 Fields in my data set with, let's say, an average of 100 Field Values per Field, that's potentially 40,000 configurations you're asking me to make.

You could think of what I am saying as "default colours per Dimension value", but that is not accurate either because I don't care about the colour itself, I care about the colour consistency.

If that is unclear, I'm happy to try to explain further.

Thank you.

John_Teichman
Former Employee
Former Employee

Hello @BradMazurek ,

Thanks for the additional feedback. There are actually two ways to achieve this in Qlik Sense. The first is as described in the link I sent. The second method is to enable "persistent colors" in your visualizations.

persistent_colors.png

While not "automatic", enabling persistent colors in your visualizations will keep your dimension value colors consistent across all visualizations that have the option enabled. You can see additional information here:  

https://help.qlik.com/en-US/sense/November2019/Subsystems/Hub/Content/Sense_Hub/Colors/examples-visu...

 

 

 

Status changed to: Open - New
BradMazurek
Contributor II
Contributor II

Hi @John_Teichman ,

I will check out that other functionality you describe.

But I must ask: If that functionality is available, why wouldn't it always be enabled? What is the use case for having it disabled? Even if such a use case is there, why wouldn't the default behaviour be to have it enabled The current behaviour would seem to imply the use case for having it disabled is more important to support than the use case to having it enabled.

Thanks, John.

John_Teichman
Former Employee
Former Employee

Both cases are strong and one can make an effective argument for either side. The important thing is that the capability is available for use. The philosophical debate about what the default behavior will probably continue, but not be resolved any time soon. 😀

Status changed to: Closed - Already Available