In the July 2025 Power BI update, the Shape formatting option was removed from the Button Slicer visual. This change has significantly impacted the ability to customize the appearance of slicers, especially for users who rely on rounded or pill-style buttons for consistent UX design.
While layout and style settings (e.g., Card vs Table) remain, they do not offer the same level of visual control previously available through the Shape dropdown or border radius settings. Existing reports still retain their shaped buttons, which confirms that the underlying formatting logic is still supported — it's just no longer exposed in the UI.
This change:
- Reduces visual flexibility for designers.
- Breaks consistency with existing reports.
- Removes a feature that was widely used and appreciated.
Request: Please consider restoring the Shape formatting option or providing an alternative method (e.g., via theme JSON or advanced formatting) to control button shape directly. This is a small but important feature for maintaining visual polish and user experience in dashboards.
Thank you for your continued improvements to Power BI — this feedback comes from a place of appreciation and a desire to keep the platform as flexible and powerful as possible.
2 Comments
- kleighResponsive Resident
It seems the solution is here:
Advanced Slicer Visual Theme Issue | Microsoft Fabric Community
"$id": "default" is required, even if you aren't setting overrides for other states. - kleighResponsive Resident
If the layout is set to "Tiles" then the option appears ... if it's set to Table then it disappears. I can't seem to make it work with the JSON. I've looked at the schema, tried many things but the options do not seem to take.
Recent ideas
Data Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v1 day agoCommunity ChampionNew619Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v1 day agoCommunity ChampionNew21Views1like0CommentsBulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal1401971 day agoFrequent VisitorNew6Views0likes0Comments