I’m working with visual Highlighting in QuickSight and noticed behavior that I can’t fully explain.
I have several visuals on a dashboard.
When I click REJECT in the first visual, QuickSight highlights REJECT across all other visuals — this is expected and correct.
However, if another category (e.g., FRAUD) has the same percent, then QuickSight also highlights that category in the other visuals, even though I selected only REJECT.
When I use only count in my visuals works ok, but when I add the percent it behaves this way.
Why does QuickSight Highlighting behave this way?
Why does it highlight multiple values when their aggregated values match?
Is this expected behavior?
Is there a way to force Highlighting to apply only to the dimension I clicked, regardless of matching counts?
Hello @Teodora, this is really interesting. It seems like it is highlighting based on the value, rather than the group by. Is your field that is returning Accept, Refer, Fraud, and Reject a dataset column or a calculated field?
I am noticing that Fraud and Reject are returning the same values in both percentage and number, so is it safe to assume that both are always true at the same time. My thought is the way those 2 specific values are linking is causing the visual to highlight both. I don’t believe you would always see this when percentage values match.
Just checking back in since this thread hasn’t received a response in a while. Were you able to find a solution yourself in the meantime or are you still facing the same issue? Please help the community by marking this answer as “Solution” or following up in general within the next 3 business days!
Hi, I am still facing this issue. It seems that the highlighting is based on the dimension and the value, if equal. My expectation is that the highlighting should be based on dimension only. What is the expected behavior?
I’ve built navigation actions that set a parameter based on the user click, then set the colors in the chart to make it look like that is actually being highlighted. It has been a decent work-around when the default functionality doesn’t work as anticipated.
Hello @DylanMorozowski, thank you for proposal. I have few questions though.
First you create a parameter and then change the parameter with navigation action? How do you use the parameter in the chart?
I tried to create a parameter and then calculated field to use the value from the parameter, but it requires a default value. I don’t have a default value as the data is dynamic and I don’t know the values in the field that I want to highlight. If I hard code the value it filters out all other values as well, but I want to show “All” categories in my charts and to highlight only one.
The idea is, we can set the parameter and then for a bar chart, set the color of the chart based on a calculated field. This can be used within the group by field. The only weird part is managing the filter removal process which is why I included a hidden button that appears when the user actually makes a selection on the visual. It will have it’s own navigation action that sets the parameter back to the default value of “None”.
Then, I tested out a regular filter action and grabbed the HEX code for that color with a browser extension, and edited the field colors for the calculated field. Let me know if you have any questions!
Thank you a lot for the proposal. Creating a parameter didn’t work for me, but I manage to fix the issue by changing the type of the visualization to pivot table. It looks like the issue is only with table visualizations.
