Bookmark Navigator not showing in Published Apps

[wiSama]

The recent feature "Bookmark Navigator" is not working properly when I publish my report into an app. I can't really understand what is happening because when I open my report in the PowerBI Service, it works fine, but when I publish it into the App it somehow disappears.

- Print in PowerBI Service: I can see, click it, works well.

- Print in Published App: the Visual header still showing, but the Buttons itself somehow invisible and unusable.

Did someone have the same issue? I tested it opening the report separetely in another tab and it works fine, only in the App that I can't see the new feature Bookmark Navigator.

[v-cazheng-msft]

There is an exsiting ICM.

[Anonymous]

If you are having this issue pending the team fixing it - even if the bookmarks are not showing on the visual you can still get to them using the Bookmarks/Show more bookmarks on the menu in the app (rather than reverting to an older version of your report that does not use the navigator which is where I nearly headed to).  I guess most people realise this but for anyone like me who had not realised, well, maybe it is of some help as a stop gap.  Assuming it gets fixed soon of course.

[alexrowntree]

I've also been having the issue with Bookmark Navigator not showing in Published Apps. I was able to fix it by clearing my browser cache, but I'm still worried that my users will not see the bookmarks unless they clear their cache which is not a good experience at all!

@Microsoft please ensure the bookmark navigator is fully tested and fixed in a future update as its an extremely useful feature when it works!

[rebeccaETE]

Any update on this issue? An ETA on a fix perhaps?

I'm also facing this issue with a report I'm soon to deliver to the stakeholders. I would like this to be fixed before then, otherwise I'll have to revert to using buttons again.

[Anonymous]

Any update on this issue? An ETA on a fix perhaps?

Seconded.  This needs fixing urgently.   

[Anonymous]

Agreed, i've got this in my published reports and its causing a lot of confusion with the users

[v-cazheng-msft]

Hi  All,

According to the exsiting ICM, this issue should have been resolved. If you still have this issue, please consider opening support ticket as I mentioned earlier. There will be a support engineer assigned to you on such issue and they will troubleshoot with you.

Best Regards,

Community Support Team _Caiyun

[Anonymous]

I dont think the issue was ever actually understood by support.  Anyone going for a ticket? - presume they don't want all of us wading in.

[rebeccaETE]

I can open a ticket. I will reference this post as well to highlight the urgency. 

[rebeccaETE]

Done, I'll keep you posted.