Skip to main content
Microsoft Idea

Power BI

Needs Votes

When creating bookmarks, affecting report level filters should be optional

Vote (44) Share
Marlou Kruit-van der Velde's profile image

Marlou Kruit-van der Velde on 27 Oct 2017 16:31:29

We use report level filters using URL filtering in Power BI embedded. Overriding these with bookmarks kills the entire purpose of the dashboard. Report level filters should not be affected by bookmarks or it should be optional choice when creating the bookmark.
Bookmarking is useless for us with the current behaviour.

Comments (2)
Marlou Kruit-van der Velde's profile image Profile Picture

Bernhard Essletzbichler on 21 Mar 2024 13:29:53

RE: When creating bookmarks, affecting report level filters should be optional

Similar case here,would greatly benefit from this.I use custom URLs in an Alerting process to send Users direclty to the account in question within our main report.I am struggeling quiet a lot to get the links working in a table manner.If anyone has tips, please let me know.

Marlou Kruit-van der Velde's profile image Profile Picture

Tas Ranson on 05 Jul 2020 23:05:36

RE: When creating bookmarks, affecting report level filters should be optional

I think my use case is similar.

We use Custom URLs on dashboards to send users to pre-filtered versions of reports.

On these reports we have a Navigation Page that uses Images (of buttons) linked to bookmarks to navigate to various pages of the report.

We would like to use an Image tile on many dashboards (that point to the same report) and have it go to the Navigation page of the Report, with its URL filter. We then want the user to be able to click the buttons on the Nav page and jump to various report pages, BUT retain the URL filter. Currently, since the Bookmark applies the filters it was saved with, it in effect ignores the URL Filter, though the URL filter remains in the Browser URL.

It would be great if the Bookmark could be set to accept the existing filters (including URL ones) and just change the page.

We have a current workaround which is to hit refresh on the browser after the Button has navigated via the bookmark to the new page. However this means the users initially see the wrong set of data.