Forum Discussion
Power Bi on Teams glitch
There seems to be a glitch in Power Bi on Teams, the visuals appear to be disturted. But when i view same report on the web browser, it appears fine, and when I view the original file on desktop, it also appears fine.
Hi leroyo ,
Thank you for the detailed explanation and the screenshot - that really helps clarify the issue you're encountering.
Based on your description and testing, it appears this is a rendering inconsistency with the new Card visual (Preview) in the Power BI Service, particularly when accessed via Microsoft Teams or browser. Specifically, when the default Callout value is turned off and replaced with an enlarged reference label, the Callout value unexpectedly reappears in the published version - creating a duplicate display and disrupting the intended layout.
If the report is part of a Power BI App, please make sure to update and re-publish the app after making changes to the report. Otherwise, updates may not be reflected for reports in apps.
We’d like to highlight that this is part of a recently acknowledged Known issue:
"Power BI customers using the new Card and Button Slicer visuals may experience issues where Callout values appear in the Power BI Service even after being turned off in Desktop."
Shared Workaround: Need to manually turn off call out values for Card & Button Slicer visuals in Power BI Service.
This confirms that the behavior you’re seeing is currently under review and may be addressed in a future update to these preview visuals.
As an additional workaround, instead of turning off the Callout value, I set its color transparency to 100% in Power BI Desktop.
This hides the Callout value, and when published to the Power BI Service, it remains hidden and avoiding the duplicated visual issue.
If you’re using a reference label as the main display, this could serve as a reliable workaround until the preview behavior is improved.
Please reach out for further assistance.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and a kudos would be appreciated.Thnak you.
Thank you for your help.
I ended up redesigning the entire report and publishing a new version to the App, while hiding the previous version that had the error so I could monitor it. It does seem to have been a rendering issue, as the visuals on the original report are now displaying correctly - so perhaps the issue has been resolved.
I'll continue using the new report moving forward and will take some time to carefully explore the new card visual.
Thanks again!
7 Replies
Update: I just realized that this glitch seems to only be on the new card visual.
v-veshwara-msftCommunity Support
Hi leroyo
Thank you for reaching out in Fabric Community and thanks for sharing the update.
The new Card visual is currently in Preview and is only available in Power BI Desktop for direct creation and editing. (new) Card visual considerations & limitations - Power BI | Microsoft Learn.
However, once created in Desktop, it can be published and viewed in the Power BI Service and Teams.
Since you are experiencing visual distortions specifically within Microsoft Teams, please try the following steps:
Refresh the Report in Teams.
Adjust Scaling (Zoom) in Teams.
Ensure your Microsoft Teams is updated.
Try republishing the report from Power BI Desktop and check if the issue persists.
Also try checking the report in Teams web browser. If it appears correctly in web browser, the issue might be related to how Teams renders the report.
Please try the above steps and reach out for further assistance.
Hope this helps.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and a kudos would be appreciated.Thank you.
Hi
Thank you for your response and for the helpful suggestions.
I’ve now tried all the steps you mentioned - refreshing the report in Teams, adjusting the scaling, confirming Teams is up to date, republishing the report from Desktop, and even checking the report via the Teams web browser. Unfortunately, the issue still persists.
To give a bit more context, I always design my reports in Power BI Desktop, and for this one, I used the new Card visual specifically to take advantage of the ‘detail’ function available in the reference label. I turned off the default Callout value and instead created multiple reference labels. I then used the topmost reference label, increased its size and repositioned it to simulate a callout value, while the others retained a smaller size. This allowed me to include a conditional detail, such as an arrow, in a way the default Callout value doesn’t allow.
However, once I publish the report to the Power BI Service and view it via the App - either in Teams or directly in the browser - the originally hidden Callout value becomes visible again. This results in two values appearing: the default Callout value (which I had turned off), and the large reference label I designed to take its place. This creates a distorted or glitch-like effect in the report's layout.
I’ve attached an image to help illustrate the issue - the bottom value is the enlarged reference label I intended as the primary display, while the top value is the original Callout value that was hidden in Desktop but reappears in the Service.
Thanks again for your help, and please let me know if there’s any workaround.
Hi v-veshwara-msft
Thank you for your response and for the helpful suggestions.
I’ve now tried all the steps you mentioned - refreshing the report in Teams, adjusting the scaling, confirming Teams is up to date, republishing the report from Desktop, and even checking the report via the Teams web browser. Unfortunately, the issue still persists.
To give a bit more context, I always design my reports in Power BI Desktop, and for this one, I used the new Card visual specifically to take advantage of the ‘detail’ function available in the reference label. I turned off the default Callout value and instead created multiple reference labels. I then used the topmost reference label, increased its size and repositioned it to simulate a callout value, while the others retained a smaller size. This allowed me to include a conditional detail, such as an arrow, in a way the default Callout value doesn’t allow.
However, once I publish the report to the Power BI Service and view it via the App - either in Teams or directly in the browser - the originally hidden Callout value becomes visible again. This results in two values appearing: the default Callout value (which I had turned off), and the large reference label I designed to take its place. This creates a distorted or glitch-like effect in the report's layout.
I’ve attached an image to help illustrate the issue - the bottom value is the enlarged reference label I intended as the primary display, while the top value is the original Callout value that was hidden in Desktop but reappears in the Service.
Thanks again for your help, and please let me know if there’s any workaround.
- v-veshwara-msft
Hi leroyo ,
Thank you for the detailed explanation and the screenshot - that really helps clarify the issue you're encountering.
Based on your description and testing, it appears this is a rendering inconsistency with the new Card visual (Preview) in the Power BI Service, particularly when accessed via Microsoft Teams or browser. Specifically, when the default Callout value is turned off and replaced with an enlarged reference label, the Callout value unexpectedly reappears in the published version - creating a duplicate display and disrupting the intended layout.
If the report is part of a Power BI App, please make sure to update and re-publish the app after making changes to the report. Otherwise, updates may not be reflected for reports in apps.
We’d like to highlight that this is part of a recently acknowledged Known issue:
"Power BI customers using the new Card and Button Slicer visuals may experience issues where Callout values appear in the Power BI Service even after being turned off in Desktop."
Shared Workaround: Need to manually turn off call out values for Card & Button Slicer visuals in Power BI Service.
This confirms that the behavior you’re seeing is currently under review and may be addressed in a future update to these preview visuals.
As an additional workaround, instead of turning off the Callout value, I set its color transparency to 100% in Power BI Desktop.
This hides the Callout value, and when published to the Power BI Service, it remains hidden and avoiding the duplicated visual issue.
If you’re using a reference label as the main display, this could serve as a reliable workaround until the preview behavior is improved.
Please reach out for further assistance.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and a kudos would be appreciated.Thnak you.
Thank you for your help.
I ended up redesigning the entire report and publishing a new version to the App, while hiding the previous version that had the error so I could monitor it. It does seem to have been a rendering issue, as the visuals on the original report are now displaying correctly - so perhaps the issue has been resolved.
I'll continue using the new report moving forward and will take some time to carefully explore the new card visual.
Thanks again!