Quicksight bookmarks lost on dashboard update

Hi,
We are using cdk to deploy QS dashboard and analysis. We use the UI to update the analysis, use describe-template to create a template and we use this template to deploy to a dashboard. All our datasets and datasource also reside as part of our cdk construct along with the template_definition.

The issue we are facing with above process is, everytime we update the analysis and create a new template to publish to dashboard through cdk, we are losing user bookmarks. Not sure if this deletes and recreates the dashboard. How do I get around this?

Thanks for your question @vairang! And welcome to the Community! :slight_smile:

@DylanM and @duncan could you look at this Monday morning?

1 Like

Hello @vairang , welcome to the Quicksight community!

My understanding is that if you use cdk to recreate a dashboard, once the user logs on to that new dashboard version they are going to lose their bookmarks. To clarify, are you updating all of the assests with cdk, (analysis and dashboard) or just the analysis and then publishing to dashboard via the console?

I can mark using cdk to publish dashboards and retain user bookmarks as a feature request for the Quicksight team!

1 Like

I duplicate the deployed analysis, modify the analysis via console. Use create-template and describe-template-definition to pull the template from the modified analysis.

I add this template to my cdk package. Now using cdk construct I create analyses from this template and then using the created analysis I publish it to my dashboard again using cdk constructs.

I see that we need to update the dashboardId every time to get the new template deployed to the dashboard. I think during this process the existing dashboard is deleted and new one is created which makes us loose the user bookmarks

@vairang
The bookmarks are tied to the dashboard id. When the dashboard id changes, QuickSight treats it like a new dashboard and doesn’t keep the bookmarks. Is it possible for you to update your workflow to update the existing dashboard instead of replacing it by a new one?

Yes. We tried not generating a new dashboard id through cdk everytime. But what happens then is, its assumed that there is no change to the dashboard and the dashboard is not published with the new template. Unsure if its cdk that doesn’t consider it as a change. Can you suggest a work-around for this?