We are using QuickSight embedded console in our custom web site. When we add custom filters to a visualization, single sheet or cross-sheets and apply those filters, we want to be able to have this filter saved as part of a bookmark. However, if we create a new bookmark or update an existing one, even though the bookmark seems to save successfully, when we return to the dashboard and apply the bookmark, the filter is not applied. Isn’t this the point of the bookmark, to persist filters applied by the user? Are we doing something wrong?
Here are the steps to reproduce:
Open dashboard
Navigate to sheet
Click the filter icon/button
Choose “Add Filter”
Choose a field
Apply some filter to the field
Set the filter to visual, sheet or cross-sheet (does not seem to be matter which)
Apply the filter → filter is applied correctly
Save a new bookmark or update an existing bookmark
Refresh the page or reset the dashboard to the original
Click the bookmark icon/button
Select the newly saved bookmark
Previously created bookmark is not applied and is not found in the filters pane
Please let us know if there is something we are obviously missing. Thank you in advance.
When you’re embedding, are you embedding for registered or unanimous users? If your embedded environment does not require a login, that would most likely be the reason. Filtered bookmark views are reserved for registered users as the system utilizes the user name to store the bookmarks with specific values set.
I’ve also verified that this ignoring filters in bookmarks issue exists in the full AWS/Quick console scenario (not using embedded dashboard). Can anyone verify if this functionality works for them? It seems like this has to be a bug in QuickSight.
I noticed this last year, and raised a support case for it. It got marked as a feature request unfortunately.
This could be superseded potentially by the createSharedView() api. You’d have to manage the views outside the frame, but if you are embeded, it maybe an option.
I just tested this out by making a new bookmark and it saved all of my control selections without any issue (standard dashboard, not embedded).
I believe I may have overlooked this in my initial response; are you using parameters to handle the filtering?
If not, I believe that would be the reasoning why. Bookmarks are simply saving a specific url that gets created for your page. Parameter values get stored in that url, therefore saving the selections within your bookmark. Where filters just get applied to a specific visual, but do not alter the url, so they do not get saved.
I’m not sure I follow the association of bookmarks to parameters. We are not using parameters in any way, but the documentation regarding bookmarks claims “…make changes to the filters or parameters, or select the sheet that you want”. I did get a response from AWS that ad-hoc added filters are not supported by bookmarks, but filters available in the filter pane should work.
You are correct that changes within the “Controls” section work correctly with bookmarks, but changes within the filter pane do not seem to be working.
Hi @steve.waffensmith,
The filter icon/button available on the dashboard is for the ‘ad-hoc’ filtering. That option is only available if you enable that feature when publishing. So that would be the option that is not supported according to the other response you received.
If you want to give your reader the option to customize for bookmark saving, I would suggest incorporating controls, you can place them in a control panel so that they give a similar feel to the ad-hoc filtering option.
Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime.
If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.
I opened a case with AWS. They state that bookmarks do not work with the filter pane and only work with the control panel filters. Not really ideal if you have many filters available for your users. I pushed this through as a feature request.