TLDR: When using nested bookmarks with a Bookmark Navigator, the navigators highlighted button does not reset when a higher-level bookmark is triggered, causing mismatches between what is displayed and what is selected.
Suggestion: allow bookmarks to also control the state of navigators, keeping them synchronized.
Currently, when using the Bookmark Navigator together with other bookmarks configured only for "Display" and "Selected visuals", there is a synchronization issue.
Practical example:
I have a top-level bookmark that shows/hides groups of visuals, including a bookmark navigator inside that group.
Inside this group, the internal bookmark navigator allows switching between Bookmark 1 and Bookmark 2.
If I use the internal navigator to switch to Bookmark 2, the corresponding button is highlighted correctly.
However, when I go back to the top-level bookmark, the visuals return to the Bookmark 1 scenario, but the navigator button still shows Bookmark 2 as active.
This creates confusion for the end user because the state displayed on the screen does not match the navigator’s highlighted button.
Improvement suggestion:
Add an option so that the Bookmark Navigator automatically synchronizes with the state saved in the bookmark, just like other selected visuals. This way, when a top-level bookmark is triggered, any internal bookmark navigators would also update their active button to match the bookmarks state, avoiding inconsistencies between the displayed scenario and the navigator. This improvement would bring much more clarity to navigation, especially in complex reports that use hierarchies of bookmarks and nested navigators.
Recent ideas
Programmatic point-of-failure recovery for Fabric pipelines
The Fabric monitoring UI already supports Rerun → rerun from failed activity. That capability is only reachable by a human clicking in the portal. Please make point-of-failure recovery available to a...EversonElias4 hours agoRegular VisitorNew6Views1like0CommentsEnable Managed Private Endpoints Support for Microsoft Fabric Capacities Below F64
Managed Private Endpoints in Microsoft Fabric are currently supported only on F64 and higher capacities. Customers using lower capacities, such as F8, cannot establish private connectivity to Azure s...v-tsindhu5 hours agoMicrosoft EmployeeNew7Views0likes0CommentsAccessibility bug: Notebook cell text becomes invisible under Windows 11 High Contrast mode
Any text written inside a Fabric notebook is invisible when Wndows High contrast mode is enables. This applies to cell text only (not the UI). In addition, auto-complete windows are not respecting t...abigb7 hours agoNew MemberNew3Views0likes0Comments