Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

March 2025 update - Style preset error

Helo

With the March Update we are facing the following error on our visuals (on JSON file)
Style Preset not found - click on details

the selected style preset did not have a definition the report's custom theme definition. 

How can we solve this?

Status: Delivered
Comments
TrevPBI
Regular Visitor
I have the same issue
sandeeppolsani
New Member
I'm facing the same, using pbip format
MR24
Regular Visitor
Same issue !
AyAyron
Regular Visitor
same issue
Anonymous
Not applicable
We are having the same issues with all of our embedded Power BI reports. What should we do in our organization?
MR24
Regular Visitor
Hi Microsoft, Still no answer ! This is not acceptable and needs to be fixed ASAP. We have many reports in our organisation using the "Card (new) " visual that are now broken.
Anonymous
Not applicable
https://github.com/microsoft/powerbi-desktop-samples/tree/main/Report%20Theme%20JSON%20Schema The last JSON schema is from February - I believe that's why the JSON theme we have does not show any errors while comparing it to the schema but Power BI is flagging errors
tiagotfsilva
New Member
Is there a fix already?
Anonymous
Not applicable
Our report theme was validated according to new schema published yesterday, it passes the schema validity, but the reports still breaks, we can't add new visuals or change existing ones
mattlee
Microsoft Employee
Status changed to: Investigating

To clarify, are you seeing the Warning icon show up in the Visual Header, with text "Style preset not found"?
This is likely due to double-wildcard stylePreset value in your theme file, like:
"*" {

   "*" {

      "stylePreset" {[

         "name": "Flashy Rows"

This used to only apply for Table and Matrix, which shared the same stylePreset options, but now we will try to apply this to all visuals. Since many visuals do not have a stylePreset defined, it will fail to find one and warn you about this. stylePresets for all visuals was just released last week. We will consider only showing this warning in Edit mode, it is not that useful for read-only users.

To fix this, use visualType names specifically for default stylePresets and re-upload your theme.
Note: the latest theme schema update has made validation a bit more strict, so you may need to fix other errors before you can upload themes you have used in the past.