Power Bi on Teams glitch

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!