fillter button condition formating colour

[DEngg]

I am already using condition formatting colour for the filter button and it works perfectly.
But, till today, any upgrade in the button formating so, my condition formating for colour is erase so, I am try again to build condition formatting for fill colour but after saved I am restart the report then again erase the condition formating. i don't no why this is problem occurs.

Note : I checked and its Upgrade like 
            Series
                 State  also include advanced for interaction state

Help : @eileen_iTalent , @v-ssriganesh , 

[AlenaT]

Hello @DEngg, do you mean "Button Slicer"? If so, I faced the same issue since the latest update (2.143.878.0 64-bit (May 2025) and found out that it was previously raised in another thread. However, based on the comments, it is related to the cases when a custom theme is used: https://community.fabric.microsoft.com/t5/Issues/New-Button-Slicer-Formatting-Options-in-Service/idi.... I am facing the issue that any usage of conditional formatting in "Button Slicer" (through measure or using rules, etc. ) is lost after publish. Even when I try to update it directly in the browser, it disappears after a refresh. It is a blocker for me as I apply color coding using measures, and now button slicers look broken. Microsoft team, @mattlee, please help!

[AlenaT]

I have applied the next workaround to move forward: 1) rolled back Power BI Desktop to the April version (a colleague shared the version downloaded in April and as another option: download it from the official MS archive: https://learn.microsoft.com/en-us/power-bi/fundamentals/desktop-latest-update-archive?tabs=powerbi-d... , direct link is: https://download.microsoft.com/download/8/8/0/880BCA75-79DD-466A-927D-1ABF1F5454B0/PBIDesktopSetup-2...), 2) restored the version of my Power BI report to have the version that was not opened under May version of PBI Desktop. It will give more space to have this issue fixed by the MS team in one of the next releases.

[mattlee]

This has been fixed