When creating an analysis using a definition, filters that were included in the definition are not present in the resulting analysis.
Steps to reproduce:
In the console, create a filter for a visual in an analysis
Export the definition for that analysis with describe-analysis-definition
Create a new analysis from that definition
The result will be an analysis without filters.
This was working as recently as Friday (09/22/23). I am using the AWS Ruby SDK v3, calling create_analysis. Our use case is we use a definition to load a default analysis for our authors.
Hello @SamDesmondKing, welcome to the QuickSight Community! So you said this is something that was working as expected up until last Friday? Is it possible any of the parameters related to the filters has somehow changed in your definition or maybe something within the underlying dataset? Maybe a column was removed from the dataset that a filter was linked to and it broke?
If nothing changed about the datasets, datasource, or parameters, 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. Hope this helps!
I don’t believe it’s an issue with the dataset. When you create a filter for an analysis in the console, export the definition for that analysis, then use that same definition to create a new analysis for the same dataset, the filter is not present in the new analysis.
I could be wrong but based on the above I strongly believe this is a bug in QuickSight.
I’ll reach out to support and update here with the result for anyone facing the same issue.