dashboard filters not working after dataset rename: binding broken error troubleshooting

TL;DR

Rebind the filters to the renamed dataset before rebuilding anything. A rename breaks the stored binding between the filter control and the dataset field, so open each filter, reselect the field from the renamed dataset, and republish the dashboard. Test every filter once, because a rename usually breaks all of them the same way.

dashboard filters not working after dataset rename: binding broken error troubleshooting

Use this when

• Filters stopped responding immediately after a dataset rename or republish.
• The filter control renders and accepts values, but charts never change.
• The dashboard was promoted from a development workspace where the dataset name differed.

Not for this skill when

• A single chart ignores a filter it was never configured to receive. That is a design setting, not a broken binding.
• Filters work but return wrong values. Check the field logic rather than the binding.

Steps

1. List the dashboard filters and the dataset fields each one should drive, using the pre-rename version or documentation if available. Verify: every filter has a named target field to rebind to
2. Open the filter configuration and reselect its field from the renamed dataset, even if the displayed name looks unchanged. Verify: saving the filter records the current dataset identifier
3. Repeat the rebinding for every filter on the dashboard, including hidden and defaulted filters used by drill pages. Verify: no filter still references the old dataset name
4. Republish or save the dashboard and open it as a viewer, then change one filter value at a time. Verify: each change visibly updates the charts it controls
5. Check cross-filter and cascading settings that depended on the old binding, and reselect their parent fields as well. Verify: child filters refresh their value lists when the parent changes
6. Compare a filtered total against a direct query on the renamed dataset for the same selection. Verify: the dashboard total matches the direct query total

Why it happens

Bindings are identifier based, so a rename that looks cosmetic to authors is a breaking change to stored dashboards. Tools that republish a dataset as a new object make the break total, while in-place renames break only some references, which is why the failure can look partial. Treating dataset renames as a migration, with a rebinding pass over dependent dashboards, prevents the silent version of this failure.

Dashboard tools store filter bindings against dataset and field identifiers. Renaming a dataset, republishing it as a new object, or promoting a dashboard between environments can leave the filter pointing at an identifier that no longer resolves. The control still renders, which hides the break, but selections never reach the queries. Rebinding reselects the field under its current identifier and restores the link.

Variants and edge cases

dashboard filter binding broken after dataset rename fix

The lower-case symptom phrasing matching the original report.

filters stopped working after republish rebind fields

The republish variant where a new object replaced the old dataset.

dashboard promoted filter not working different workspace

The environment promotion variant of the same binding break.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_oUfv8kPl2ht3bdP0Z7fInA