I’m facing an issue where my QuickSight dashboard visuals update correctly when I pass a dataset parameter through the URL (for example #p.vAccountId=18), but the filter controls (dropdowns or list filters) don’t refresh — they keep showing values from the default parameter value.
Key points:
The dashboard uses Direct Query.
The dataset parameter (e.g. vAccountId) is correctly mapped to the analysis parameter.
Visuals update as expected when the parameter changes.
Filter controls do not refresh and still display the values from the default dataset context.
Tested with URL navigation, browser refresh, and across users — issue persists.
It seems that QuickSight only refreshes visuals when parameters change, but not the filter control options themselves.
Question:
Is this a known limitation or is there a way to force filter controls to refresh when a parameter value changes (for example, when passing parameters via URL navigation or actions)?
@LuisBorrego Thanks for reaching out. I entered your issue into our Community chat agent and this is what I got. I have asked @Brett to validate this when back online on Monday – but hopefully in the meantime this will help you get unblocked.
This is a known limitation in Amazon QuickSight when using Direct Query datasets. When a dashboard uses Direct Query, the filter and parameter controls cache their value lists, and this cache is not cleared when you adjust dataset parameters. 1
While the visuals re-query the source and update correctly when parameters change, the filter controls remain connected to the default parameter values. 1
The filter value cache refreshes automatically every 24 hours, but it doesn’t update immediately when dataset parameters change. 1
This means that even when you pass parameters via URL, the filter controls will still display values from the default dataset context.12
To work around this issue, you have a few options:
You can add parameter values directly to your URL to have the page load with predetermined parameters. 2
Consider implementing Row-Level Security (RLS) if the parameter values are user-specific, which would ensure the proper values are displayed in controls. 3
You could try using cascading filters with the “Show relevant values” button to help manage what appears in controls based on parameter selections. 3
For Direct Query datasets, you may need to manually refresh the controls in the control bar for new values to appear after parameter changes. 1
The documentation on refreshing data in Amazon QuickSight provides additional information about managing data refreshes for both SPICE and Direct Query connections. 14
I really appreciate the response. Seeing your comments and suggestions, I realize this is a long-unresolved bug.
The option to wait 24 hours for the cache to clear doesn’t apply to waiting for it to update.
Regarding the proposed solutions:
It doesn’t work, as it displays the correct content for charts and tables, but not for filters;
I’ll be testing this; it makes sense to me;
Using cascading filters doesn’t work either;
Manual refresh doesn’t work either;
I’ll wait until Monday to see how to resolve this.
Hi @LuisBorrego,
I wonder if there’s some way to work around this using customSQL; take a look at the attached article and let me know if this could apply to your scenario:
In the dataset, add the parameter that will segment the data.
In the Analysis section, create the necessary calculated campuses that will be used as filters in the Analysis and Dashboard sections. The definition is as follows: [ifelse(ColumnSource = ${vColumnParameter}, trim(ColumnFilter), NULL)]
Add it as a filter;
Add it as a visual control;
Confirm that it has the MULTIPLE DROPDOWN option;
And that’s it!
It’s worth mentioning that many variants of this test were run, but it’s working now, and we’re done.
Question: