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
Invoke Pipeline Task - Workspace Identity Authentication
Currently, the Fabric Data Factory Invoke Pipeline task uses the user's credentials who saved the pipeline to then authenticate to the Azure Data Factory to execute the ADF pipeline. When that user'...dzebrowitz4 hours agoAdvocate IPlanned1.8KViews61likes5CommentsFabric Pipeline should run as workspace identity
Currently, Microsoft Fabric pipelines run under the identity of the last user who modified them, which can cause disruptions when tenant administrators make changes to security policies, such as enab...pellitteris4 hours agoAdvocate IINew1.4KViews27likes3CommentsBring Back separating Power BI artifacts on a per web page basis
Previously, the ability to have different artifacts open on different web tabs was enabled. This was beneficial if you wanted to differentiate what environments you were in, working across three diff...zoe-dean5 hours agoNew MemberNew53Views8likes0CommentsREST API Should expose credentials used in connections
When a consultant leaves a client, it's important to clean up any connections that may have the consultants credentials embedded within. I'm able to use the Fabric CLI to get the managed connections ...PeterDaniels5 hours agoAdvocate IIINew19Views7likes0CommentsExpose full activity-level error details in Workspace Monitoring Eventhouse
Microsoft Fabric Workspace Monitoring exposes activity-level pipeline telemetry in FabricDataPipelinesActivityRunsLogs, including PipelineRunId, OperationId, ActivityIterationCount, ActivityName, Act...MarcoOnnis6 hours agoNew MemberNew3Views0likes0Comments