Jake Carville on 21 Jan 2019 17:49:55
This idea has come about from the introduction of personal bookmarks in the PBI Service: https://powerbi.microsoft.com/en-us/blog/announcing-personal-bookmarks-in-the-power-bi-service/
Many report creators use bookmarks as a dynamic way of showing/hiding visuals, or navigating between tabs. Exposing an end user to these bookmarks could be confusing for them and expose the underlying workings of the report.
Personal bookmarks are great, but an option in PBI Desktop to expose certain bookmarks in the PBI Service would satisfy both report creators and consumers.
- Comments (68)
RE: Control which bookmarks are viewable in the service
This is crazy. We have all this great functionality we're leveraging to create a seamless experience for end users, and then god forbid they want to create their own bookmarks, they see dozens of meaningless ones!
RE: Control which bookmarks are viewable in the service
This would help reduce confusion for users.
RE: Control which bookmarks are viewable in the service
This is essential. Users always try to use them, without knowing what the bookmark is about. Hide "report bookmark" to avoid unnecessary confusion.
RE: Control which bookmarks are viewable in the service
Someone please enable this. our users shouldn't be seeing the button navigations pane.They should only see personal Bookmarks
RE: Control which bookmarks are viewable in the service
Great Idea. Even replicating the show/hide button for filters would be great.
This is needed to hide any kinds of navigational/filter state/information box types of bookmarks from the end user.
RE: Control which bookmarks are viewable in the service
Bookmarks should be categorised. It certainly helps uses but report writers need a different type of bookmark that should not be exposed to users in any circumstances.
RE: Control which bookmarks are viewable in the service
10 Pages in a report with 10 bookmarks in each page = 100 bookmarks visible in all pages.
This is good but it is not good for a developer because if we want to assign a bookmark to the action property of a button in the 10th Page or any page, we will have to scroll through the long list of 100 bookmarks.
We can group bookmarks but we can't select a bookmark from the bookmark group to fix the above issue.
There should be an option to select the bookmark group prior to the book mark selection. if no group is selected, list all bookmarks.
We can give A,B,C etc.. as bookmark names and it can be duplicated in other pages but if we duplicate, we will not be able to assign the correct bookmark to the action property. Duplicating the bookmark name is good but we need an option to select a bookmark from the bookmark group to make it useful.
We need two type of bookmarks, Local and Global. Local for developers and Global for end users. Adding a visibility icon to the bookmark and bookmark group can fix this issue (Like a visibility icon in the filter pan)
So, please add a VISIBILITY ICON to the bookmark and allow developers to make the bookmark selection based on the BOOKMARK GROUP.
Developers can provide meaningful name for bookmarks which are visible to the end users.
RE: Control which bookmarks are viewable in the service
Agreed this is an issue. I use bookmarks to show/hide filter pane. If a user clicks on these then they will be kerfuffled for certain! I want to teach people about user bookmarks but because of this it's too confusing.
RE: Control which bookmarks are viewable in the service
Agree
it makes users confused.
I use bookmarks for technical navigation or reasons
So please add this functionality
RE: Control which bookmarks are viewable in the service
The need for this is self evident. Just like how a report author can hide the filters pane from end users, the report author should be able to hide report level bookmarks. Why would an end user be required to be presented with distracting inner workings of the report? I can see some use cases where the showing the active bookmark might be desired (though not relevant to me) but this is really the exception to the rule. Current functionality assumes it is the other way around.