Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

Bookmark Navigator bug when published in app

The first image is my bookmark navigator working perfectly in the actual report opened directly from the folder in the service.   The second image is what it looks like currently in the published app including that exact same report.  If I update the app, the navigator will correct itself but as soon as the data refreshes as scheduled it will either lose the buttons (as below) or sometimes - really weirdly - it will pick up the bookmarks from a completely different report (one that is also published in the app).   

ruthhacche_0-1640084082575.png

 

 

ruthhacche_1-1640084082580.png

 

 

Status: Accepted

Similar issue has been submited internal(ICM:278899875), would update here as soon as possible if there is any progress about it.

 

Best Regards,
Community Support Team _ Yingjie Li

Comments
v-yingjl
Community Support
Status changed to: Accepted

Similar issue has been submited internal(ICM:278899875), would update here as soon as possible if there is any progress about it.

 

Best Regards,
Community Support Team _ Yingjie Li

abezgodov
Regular Visitor

In addition:
1. In my case, the bookmark navigator is not shown when a group of bookmarks is selected in it. If you refresh the page (F5 or CMD+R), the bookmark navigator will load.
2. If all bookmarks are selected in the bookmark navigator, then in the application in the bookmark navigator not only bookmarks from this report will be shown, but from all reports in the application.

 

Screenshots with all bookmarks are selected in the bookmark navigator

App:

Screenshot 2021-12-22 at 11.58.41.png

Report:

Screenshot 2021-12-22 at 12.01.08.png

Anonymous
Not applicable

Am also seeing similar and occasionally the navigator appears on other reports in the same App which is unacceptable. The problem goes away after a refresh.