Forum Discussion
A button which should work like a slicer
- 6 months ago
Hi,
Yes, bookmarks save the state of the report, including the slicer value, so if you create a bookmark while vessel 1 is selected, that bookmark will always return to vessel 1, so in practice you would need multiple bookmarks, one for each vessel, each bookmark storing a different slicer value, and the buttons would point to those bookmarks.
Because of this it does not scale well with many vessels, since Power BI cannot automatically increase the slicer value with a button, for many vessels it is usually easier to use a slicer.
- 6 months ago
You’d need over a hundred bookmarks because each item requires its own view with Previous and Next buttons linked to separate bookmarks. This approach isn’t scalable and would be a maintenance nightmare. The closest out of the box solution is the Play Axis visual.
Hello,
Power BI does not have a real next or previous button for slicers, so it cannot automatically move to the next vessel, but I think you can use a simple workaround.
Create an index for the vessels from 1 to 100, you can do it in Power Query or with DAX, then create a slicer using that index with single select, connect the index to your vessel table so the matrix shows only the selected vessel.
For navigation you can create two buttons, Next and Previous, using bookmarks that change the slicer selection, when the slicer changes the matrix updates and shows the next vessel.
Best regards,
Daniele
DanieleUgoCopp , thanks for responding.
But, I am not sure how the bookmarks would change the slicer.
Are you suggestion to create 100 booksmarks if you have 100 vessels to show and link each of the booksmarks with each vessel to view?
Thanks.
- danextian6 months ago
Super User
You’d need over a hundred bookmarks because each item requires its own view with Previous and Next buttons linked to separate bookmarks. This approach isn’t scalable and would be a maintenance nightmare. The closest out of the box solution is the Play Axis visual.