Some New Card Visuals not displaying in power bi service

[HMcC]

I have created a series of new card visuals in desktop to illustrate a series of KPI performance.  All have conditional formatting for values and references. These all look great in desktop but when published to the service most of these visuals have the following error message: 

Activity ID: 7130c25d-45e0-498d-8509-9a943d24aefe
Request ID: 7de5db24-d315-4592-acca-e9e999bd95ea
Correlation ID: 8ff78180-564f-4821-e3df-eddd944fd3a1
Time: Tue Feb 25 2025 13:18:14 GMT+0000 (Greenwich Mean Time)
Service version: 13.0.25358.42
Client version: 2502.3.23005-train
Cluster URI: https://wabi-uk-south-redirect.analysis.windows.net/

Interestingly, two of the 15 cards are showing fine.  

I've tried re-doing the visual, refreshing etc but nothing has worked.  Each of these required separate formatting and takes an age to do.  All of the ones which aren't showing are based on the first one, so not sure what's happening here.

Any help appreciated! 

[v-csrikanth · Accepted solution]

Hi @HMcC 
Thanks for reahcing out to Microsoft Fabric Community.
Below are few work arounds that resolve your issue.

1. If the visuals that fail have complex conditional formatting, try simplifying them and republishing.
2. Check the field used in conditional formatting is available in the dataset when published.
3. All fields used in the card visual (value, reference labels, etc.) return valid data for all possible slicer/filter selections. Use functions like “COALESCE” to handle blanks
4. Perform a full dataset refresh and republish.
5. Try copying a working visual instead of creating new ones from scratch.
6. Occasionally, Power BI service versions experiences regional issues.
7. Run the Performance Analyzer in Power BI Desktop to check if specific visuals take too long to load.
8. Optimize DAX measures if necessary.

If you are still facing any challenges, kindly provide further details, and we will be happy to assist you.

If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.

Best Regards,

Community Support Team _ C Srikanth.

[v-csrikanth · Accepted solution]

Hi @HMcC 
Thanks for reahcing out to Microsoft Fabric Community.
Below are few work arounds that resolve your issue.

1. If the visuals that fail have complex conditional formatting, try simplifying them and republishing.
2. Check the field used in conditional formatting is available in the dataset when published.
3. All fields used in the card visual (value, reference labels, etc.) return valid data for all possible slicer/filter selections. Use functions like “COALESCE” to handle blanks
4. Perform a full dataset refresh and republish.
5. Try copying a working visual instead of creating new ones from scratch.
6. Occasionally, Power BI service versions experiences regional issues.
7. Run the Performance Analyzer in Power BI Desktop to check if specific visuals take too long to load.
8. Optimize DAX measures if necessary.

If you are still facing any challenges, kindly provide further details, and we will be happy to assist you.

If the above information is helpful, please give us Kudos and mark the response as Accepted as solution.

Best Regards,

Community Support Team _ C Srikanth.

[HMcC · Accepted solution]

Hi, thanks for replying.  I re-did some of the visuals and tested individually, the first one worked so I copied that to complete the rest and they are now displaying.  This needs a fix as people can't keep re-doing things until it works, the first time I did them they worked but then they failed.  I'm just hoping it isn't a bug with the new card and it doesn't happen again.  Thanks again.

[AnkitKukreja]

Hi! @HMcC 

What do you see when you click on that error button? Any specific message or only these details? If you only get these ids then I would suggest you to raise a ticket with MS support.

[HMcC]

Hi, The error message is above.  I managed to re-do the visuals and they displayed.  Not ideal when you have lots of them to do and then re-do before it displays!  Thanks for your reply.