Issue: Conditional Formatting Changes When Replacing an Existing Dashboard

Q&A
,
1

I defined a Conditional Formatting rule for a “Completion%” field in my Analysis, which displays different background colors for text based on certain conditions.

Problem: When I publish the Analysis to a Dashboard:

  • If I replace an existing Dashboard, the text background colors in the final Dashboard are different from what I set in the Analysis.

  • If I publish as a new Dashboard, the text background colors display exactly as they appear in the Analysis.

Question: Why does Conditional Formatting change when I replace an existing Dashboard during publishing? This behavior is very strange — the same Analysis produces different visual results depending on whether I replace an existing Dashboard or publish a new one.

Steps to Reproduce:

  1. Create an Analysis with Conditional Formatting rules (e.g., background color changes based on value conditions)

  2. Publish the Analysis by replacing an existing Dashboard → Conditional Formatting colors are incorrect

  3. Publish the same Analysis as a new Dashboard → Conditional Formatting colors display correctly

Expected Behavior: Conditional Formatting should display identically regardless of whether the Dashboard is published as new or replaces an existing one.

Actual Behavior: Replacing an existing Dashboard causes Conditional Formatting background colors to change/display incorrectly compared to the Analysis.

2

Hi @echoyuan

Welcome to the QuickSight community!

I attempted to reproduce the behavior you described by applying conditional formatting in an analysis and publishing it to a dashboard. In my testing, the dashboard consistently inherited the theme from the analysis during publishing, and the conditional formatting displayed as expected in both scenarios (replacing an existing dashboard and publishing as new).

That said, I understand the experience may differ depending on your specific environment and configuration. I’d like to suggest a few things to check that may help us narrow down the cause:

  • Verify the published dashboard version - When you select Replace an existing dashboard, QuickSight creates a new version internally. However, in some cases, the latest version may not be automatically promoted as the active published version. You can verify this by in QuickSight console UI or using the QuickSight API (DescribeDashboard) to confirm that the version currently being served is indeed the most recent one.

    image
    image345×858 22.6 KB

  • Clear your browser cache - Please try performing a hard refresh (Ctrl+Shift+R) or opening the replaced dashboard in an incognito/private browser window. This will help rule out any stale cached rendering that might be displaying outdated formatting.

  • Check for saved reader interactions - If the existing dashboard previously had any reader interactions or saved visual states, some properties from the prior version may persist even after the dashboard is replaced. Resetting these interactions may resolve the discrepancy.

3

Thank you so much for providing a quick reply with the possible solutions.
I actually tried all of them and still it did not solve my problem.
In solutuion 1: The dashboard shows the correct version but still the theme does not follow the analysis.

Solution 2: I cleared cache in Google chrome but still the theme in analysis does not show up in updated dashbaord.

Solution3: I confirm I did not use any interactions in the analysis.

Would it be other reason? In the meantime, I’m asking the same question through Amazon Quick ChatAgent and did not get useful information.

4

Hi @echoyuan

I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf.

5

Hi @echoyuan

It’s been a while since we last heard from you. If you have any further questions, please let us know how we can assist you.

If we don’t hear back within the next 3 business days, we’ll proceed with close/archive this topic.

Thank you!

6

Hi @echoyuan

Since we have not heard back from you, I’ll go ahead and close/archive this topic. However, if you have any additional questions, feel free to create a new topic in the community and link this discussion for relevant information.

Thank you!