Forum Discussion
Visual-level filter resets unexpectedly after switching bookmarks
- 1 year ago
Your bookmark on the NonDM page likely has the "Data" option checked under bookmark settings. This causes the bookmark to override any manually changed visual-level filters (like your "Quarter = 2" setting) when you switch to it.
Unchecking “Data” prevents the bookmark from storing or resetting filters, slicer selections, and sorts. It will only store visual state and visibility, not filter values.After Fixing:
Go back to the visual.
Set Quarter = 2 again.
Navigate through bookmarks. It should now retain your filter setting.
Your bookmark on the NonDM page likely has the "Data" option checked under bookmark settings. This causes the bookmark to override any manually changed visual-level filters (like your "Quarter = 2" setting) when you switch to it.
Unchecking “Data” prevents the bookmark from storing or resetting filters, slicer selections, and sorts. It will only store visual state and visibility, not filter values.
After Fixing:
Go back to the visual.
Set Quarter = 2 again.
Navigate through bookmarks. It should now retain your filter setting.
- sabina67001 year agoNew Member
Thank you so much for your response — your explanation and suggestion completely resolved my issue!
As you pointed out, the "Data" option was checked in the bookmark settings for the visual, which was unintentionally overriding the visual-level filter I had manually set to Quarter = 2. After unchecking “Data” and reapplying the filter, everything worked exactly as expected. I really appreciate your clear and actionable guidance.
That said, I must admit the design behavior in Power BI seems a bit counterintuitive. It’s surprising that a bookmark assigned to a single visual can silently override visual-level filter changes, especially when there’s no obvious indicator. In my case, I missed that one of the bookmarks tied to a specific visual still had the “Data” option checked, which ended up causing the issue. Since this setting isn’t prominently visible when troubleshooting, it made the process more difficult than expected.
Thanks again for your help — it made a real difference!
Best regards,
sabina