Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Hi
I am using chiclet slicers and chord charts in my report. They were working fine when I closed down on Friday, but this morning all are invisible. When I click on one, when it just shows the outline. If I try to create a new e.g. chord chart, it shows a white box with headers, but no chart. If I click 'show as a table', all the data is there. When I add fields, it only registers the first one in the 'Build Visual' area, although I can see from the visual header that the other fields I added are there.
I have tried: restarting, removing and re-adding the visuals, testing on a new report with different data.
Version 2.129.2203.0 64-bit (May 2024)
Thanks in advance for any help.
Hi @Myusername1 ,
Thank you for reaching out to Microsoft Fabric Community.
Thank you @djurecicK2 for the prompt response.
This is a known rendering issue with AppSource visuals in Power BI Report Server Desktop May 2024 (2.129.2203.0). To fix it: update Desktop to the latest version, clear the local cache and reinstall the visuals from AppSource. If the problem persists, test in Power BI Service or contact Microsoft support. Most users see visuals return after updating or clearing the cache.
If it still doesn't solve the issue as mentioned earlier, I would suggest to raise support ticket by using Microsoft's Official Support Ticket channel by using below:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Thanks for the reply. It's a different issue to the ones you linked as theirs are working in desktop, but mine isn't. I've also investigated further and actually no visuals from 'get more visuals' are working.
I don't think I can open a support ticket as I don't have the credentials it's asking for.
Hi @Myusername1 ,
Looks like this has happened before- it might be a transient issue. I don't see anything on the known issues page about it though. You might need to open a support ticket.