Hover values display OK within Power BI Desktop but not in published web version

[kpost]

I have some "Line and clustered column" charts in a published dashboard.

What we are noticing is:

In the desktop version, the on-hover values are displaying just fine for both the columns and the lines.

In the published online version, the on-hover values display ONLY for the columns, but not the lines.

Here are screenshots of both.  (For some reason the mouse doesn't show up in the screenshots, but it is hovering over the line in both).

I have tried in both Chrome as well as Firefox.

Is there something I am missing here?  

Published Web VersionDesktop Version

[kpost]

 This is still an issue and the response I received made me believe that this is an issue with Power BI itself.  Is there a way to get in contact with Microsoft and submit a service ticket?

[Idrissshatila · Accepted solution]

Hello @kpost ,

Please log an issue to - https://community.powerbi.com/t5/Issues/idb-p/Issues

and the microsoft team will support you.

If I answered your question, please mark my post as solution, Appreciate your Kudos 👍

Follow me on Linkedin

[cgedemer]

I'm having the exact same issue (hover shows column values but not line values) and it just started within the last week for multiple users in my organization.  Previously it worked fine.  We all have Edge and no way to change browsers.

[kpost]

Glad to have confirmation that this is an issue experienced by others.  I'll be able to share that information with my organization, thank you.  Hopefully someone from microsoft chimes in.

[Idrissshatila]

Hello @kpost ,

try to edit the  report in server and check it there.

If I answered your question, please mark my post as solution, Appreciate your Kudos 👍

Follow me on Linkedin

[kpost]

I opened the report in "Edit" mode on the web version and I am still noticing the same issue even within edit mode in the web version, and also after removing and re-adding the field then saving.

It still only displays correctly in the Desktop version.  I can also remark that this problem is noticed in both Chrome as well as Firefox