Loading

Tableau Server – Changing a Parameter on a Published Dashboard Intermittently Displays the Previous Selection's Data (2024.2 branch)

Дата публикации: Jun 19, 2026
Описание

On Tableau Server 2024.2 (maintenance releases 2024.2.12 and later), changing a parameter on a published view or dashboard can intermittently fail to update the visualization, leaving the previous selection's data on screen instead of the newly selected value.

The behavior is:

  • Intermittent — the same parameter change sometimes updates correctly and sometimes does not.
  • Server-only — the identical workbook behaves correctly in Tableau Desktop; the issue appears only after the workbook is published to Tableau Server.
  • Silent — no error message is displayed. The view simply continues to show the prior selection's data, which can be mistaken for a data or workbook problem.

This commonly surfaces on dashboards that use a parameter to switch which dimension or view is displayed (for example, a parameter driving a calculated field that controls which worksheet/zone shows its data).

Решение

The only reliable resolution is to upgrade Tableau Server to 2025.1 or later, where this defect is not present.

Step 1 — Confirm the version is affected

In Tableau Server, go to Server Settings (or run tsm version) and confirm the build is on the 2024.2 branch at 2024.2.12 or later (e.g. 2024.2.14, 2024.2.23). Versions on this branch carry the defect; the issue is not present on 2024.2.11 or earlier within that branch.

Step 2 — Upgrade Tableau Server to 2025.1 or later

This defect was resolved in the 2025.1.0 release and is not present in any 2025.1+ version (or on Tableau Cloud).

  1. Review the upgrade prerequisites and steps in Tableau's documentation: Upgrade Tableau Server.
  2. Plan the upgrade with your server administrator (back up first via tsm maintenance backup).
  3. Upgrade to 2025.1 or later.
  4. Republish or revalidate the affected dashboard and confirm the parameter change now updates the view every time.

Note: There is no reliable workaround that resolves this while remaining on the 2024.2 branch, and no fix is planned for the 2024.2 branch. The upgrade is the only path forward.

Номер статьи базы знаний

005387422

 
Загрузка
Salesforce Help | Article