Missing 'disabled' state for Advanced Slicer Visuals in custom theme schema

[ChrisD_UK]

I've started using the cross-highlighting feature for Button Slicers, as released in the October 2025 update (2.148).  One of the steps for getting it to work is to set properties for the disabled interaction states of the button and the callout.  For example, 100% transparency to make the button 'disappear'.  Having got this to work using the Desktop visual property cards, I set about editing my custom theme to include these property settings, only to find that they don't appear to have been introduced into the JSON schema yet.

I'm using the 2.145 schema version from the July 2025 update.  This is the most recent version currently on powerbi-desktop-samples/Report Theme JSON Schema/README.md at main · microsoft/powerbi-desktop-sampl....  This version doesn't include the disabled state (see below - 'rest' doesn't appear to work).  On the off-chance that Desktop 2.148 recognised it, I tried to import a custom theme that included disabled interaction states.  The import failed.  I presume that this means that Desktop 2.148 is itself still using an earlier version of the schema?  Does anybody know how I can set these properties in a custom themes or do I need to wait for Desktop 2.148 or later to recognise a forthcoming schema version that does contain 'disabled' states?

        "actionStates-advancedSlicerVisual": {

            "type": "string",

            "anyOf": [

                {

                    "enum": [

                        "default",

                        "selection",

                        "press",

                        "hover",

                        "selection:selected",

                        "expansion:expanded",

                        "series:selectall",

                        "selection:unselected",

                        "expansion:collapsed",

                        "selection:unselected",

                        "interaction:hover",

                        "interaction:press"

                    ]

                },

                {

                    "pattern": "^(selection:(selected|unselected|default)|expansion:(expanded|collapsed)|interaction:(hover|press|rest)|series:(selectall))?(-selection:(selected|unselected|default)|-expansion:(expanded|collapsed)|-interaction:(hover|press|rest)|-series:(selectall))*$|^default$"

                }

            ],

            "$comment": "Enter a state for visual elements: selection:[selected|unselected|default], expansion:[expanded|collapsed], interaction:[hover|press|rest], series:[selectall], each state can be used once, separated by '-' if not first, or type 'default' if no states are used"

        },

[v-priyankata]

Hi @ChrisD_UK 

Thank you for reaching out to the Microsoft Fabric Forum Community.

@rajendraongole1 Thanks for the inputs.

I hope the information provided by user was helpful. If you still have questions, please don't hesitate to reach out to the community.

[v-priyankata]

Hi  @ChrisD_UK 

Hope everything’s going smoothly on your end. I wanted to check if the issue got sorted. if you have any other issues please reach community.

[ChrisD_UK]

Yes, all sorted thanks @v-priyankata.  I've diaried a task to check for the new theme schema in a couple of months time.  Thanks.

[rajendraongole1]

Hi @ChrisD_UK - Since you’re working in a production context (and want a stable theme import experience), I’d recommend the following strategy:

1. Use a “supported subset” of the theme JSON for now — i.e., exclude the disabled/rest interaction state settings until schema catches up.

2. Set the UI formatting manually in the report for those visuals (or via template).

3.Create a short backlog item to revisit the theme JSON once the schema is updated (expected in a future release).

Hope this helps

[ChrisD_UK]

Hi @rajendraongole1 Thanks for the response.  That's basically what I've done and I can easily live with this.  It's good to know that I'm not missing anything and that I can expect a schema update soon.  Just to round this one off, any idea how long these schema changes take to come through in a new release?  I'd assume that it might be something like a couple of months but not years.  Sound reasonable?

[rajendraongole1 · Accepted solution]

Hi @ChrisD_UK  - Exactly, sounds reasonable.
From what I’ve seen in past updates, theme schema changes usually lag a release or two behind new visual features, so a couple of months is a fair expectation. Hopefully, we’ll see it appear. 

Hope this helps.

Thank you!