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
Clone a workspace, including its data, to a new workspace
Description: Today there's no way to fully clone a Fabric workspace: git sync and Deployment Pipelines move item definitions only, not the underlying data; Warehouse's zero-copy CREATE TABLE ... AS ...gclements14 minutes agoHelper IINew2Views0likes0CommentsAllow NotebookUtils getSecret() to authenticate with Workspace Identity
Current behavior In Microsoft Fabric, notebookutils.credentials.getSecret() authenticates against Azure Key Vault using the identity of the user who executes the notebook. This behavior appli...tmihara5 hours agoNew MemberNew5Views0likes0CommentsSupport Synonyms in Fabric Warehouse
Microsoft SQL Server has a very powerful feature by the way of "synonyms." It allows users and DBAs to do all sorts of powerful magic such as rewiring objects under the hood (e.g. run the code agains...matthias-bi9 hours agoRegular VisitorNew1.3KViews18likes2CommentsExpose Refresh Warnings and Informational Messages via Notifications and API
When a Power BI semantic model refresh completes successfully, the status shows Completed, even when the refresh details contain warnings or informational messages that require attention. Please pro...Jashwanth_K11 hours agoMicrosoft EmployeeNew24Views6likes0CommentsInvoke 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'...dzebrowitz15 hours agoAdvocate IPlanned1.8KViews61likes5Comments