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

Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.

selfFilterEnabled and data.mode settings not applied in slicer visualStyles via theme

Description:

When defining a custom Power BI theme using reportThemeSchema-2.141.json, the following settings under the visualStyles > slicer > "*" section do not behave as expected:

  • general.selfFilterEnabled: Setting this to true has no observable effect. It is expected to enable or disable self-filtering in slicers.

  • data.mode: Setting this to "Dropdown" does not switch the slicer visual to dropdown mode as intended. The slicer remains in its default state (typically "List").

Theme Snippet:

    "$schema": "reportThemeSchema-2.141.json",
    "visualStyles": {
        "slicer": {
            "*": {
                "visualHeader": [
                    {
                        "show": false
                    }
                ],
                "items": [
                    {
                        "textSize": 9
                    }
                ],
                "general": [
                    {
                        "selfFilterEnabled": true
                    }
                ],
                "data": [
                    {
                        "mode": "Dropdown"
                    }
                ]
            }

 

Expected Behavior:

  • The selfFilterEnabled property should toggle the slicer's ability to self-filter.

  • The mode: "Dropdown" property should set the default slicer layout to dropdown when applying the theme.

Actual Behavior:

  • Neither setting has any effect on the slicer visual when the theme is applied.

  • All other settings in the same visualStyles block (such as textSize and visualHeader.show) work correctly.

Request:

  • Clarify whether selfFilterEnabled and data.mode are officially supported in visualStyles for slicers.

  • If supported, please investigate why these properties are being ignored.

  • If not supported, please update the documentation or consider supporting them in future schema versions.

Status: New