We have a QA team looking at multiple dashboards, they have Viewer access only.
For example, they look at Dashboard1 that includes a filter option for column1. The dashboard is being driven by a custom sql dataset connected to Redshift. Column1 is included in the query for Dashboard1’s dataset.
Our QA user now goes to look at Dashboard2. Dashboard2 is also driven by a custom sql dataset connected to Redshift. Column1 from Dashboard1 does not exist in the Dashboard2 dataset or custom sql query, however, the QA user is seeing Column1 as a selectable option in the Control/Filters when accessing Dashboard2 and refreshing the page. Column1 only disappears when another option is selected from the filter drop-down.
How do we prevent filters from other dashboard/dastasets from persisting on other dashboards when the fields do not exist in the dataset?
Hi @krushmere ,
I am assuming this is because the parameter is set to same default value across both dashboard.
To check this, you can confirm if the filter controls are powered by parameter and if so, is the unexpected value set as default value of the parameter. Also are both the dashboards sourced by single analysis and using the same parameter control ?
Thanks,
Prantika
The default value for both Dashboard1 and Dashboard2 is ‘Totals Only’. The unexpected value is not the default and the dashboards are sourced from completely different analysis and datasets.
What is the source of the values for the parameter? Does that dataset contain the field value?
The source of the parameter is a calculated field that doesn’t include the unexpected field value and isn’t sourced from the same dataset
Hi @krushmere, I’m out of ideas. Sorry, currently this is not possible without using custom coding, here are some examples:
Did this solution work for you? I am marking this reply as, “Solution,” but let us know if this is not resolved. Thanks for posting your questions on the QuickSight Community!
