Forum Discussion

ToddChitt's avatar
ToddChitt
Super User
2 years ago
Solved

Theme elements complete list

Is there documentation anywhere on the complete list of Power BI Theme JSON elements? The Customize Current Theme options is woefully lacking. Example: for Visuals, you can set the Border to be ON, but you can't set the Shadow property, which, for just about every visual is a close cousin. What is the element name for setting the Shadow properties in a JSON theme? Do we have to guess?

 

Is there documentation out there?

 

Thanks in advance

7 Replies

  • bcdobbs PijushRoy thank you both for your suggestions, good content and links.

     

    On a somewhat related topic: When I search the reportThemeSchema.json file for "Matrix" nothing comes up. However, I did come accross "pivotTable" as one of the visual elements. I'm sort of assuming the two are synonomous. Why call it one thing in the desktop design user interface, but use a totally different name for it in the theme file? That plus the fact that my Visual Studio Code does not behave as the documentation states it should here: Use report themes in Power BI Desktop - Power BI | Microsoft Learn in regard to Find Visual Properties to set is going to make this a challenging exercise.

     

    Thanks again for the tips. I'll slug through it.

    • bcdobbs's avatar
      bcdobbs
      Community Champion

      Do you mean the json isn't formatted in vs code? Should just be a case of right clicking  and then "format document".

       

      As to the naming I'm afraid I don't know.

      • ToddChitt's avatar
        ToddChitt
        Super User

        Hello bcdobbs and thanks for the response.

        My JSON document formats just fine in Visual Studio Code. The issue is centered around VS Code and pulling up the auto-complete options from the schema. The documentation shows this snippet:

        When I try the same thing, however, the list of auto-complete options is made up of elements in the preceeding JSON, not from the schema:

         

        I have traced the difference down to the fact that I am trying to modify the dropShadow of ALL (*) visualStyles, not just "azureMaps" as shown in the documentation. 

         

        My personal opinion is that the user experience has some room for improvement. 

        Again, thank you for the links.