Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.
Description:
In Power BI Report (PBIR) metadata, every visual already has an isHidden property that controls its visibility. Today, however, this property can only be set manually in the UI (via the Selection pane). There is no way to drive this property dynamically using a DAX expression.
This is a major limitation because one of the most common use cases for Bookmarks is to simulate conditional visibility (show/hide visuals depending on user selection or business logic). While bookmarks work, they are cumbersome, static, and hard to maintain at scale.
Proposal:
Enable a new “Visibility” binding for visuals in the format pane, where authors can assign a DAX measure (fx) returning TRUE/FALSE (or 0/1).
If the measure evaluates to TRUE → visual is shown.
If FALSE → visual is hidden (not rendered).
Benefits:
Much more flexibility for UX/UI design.
Reduces dependency on complex bookmarks.
Simplifies scenarios such as:
Show a chart only if a slicer is selected.
Hide detailed visuals until a KPI passes a threshold.
Display different layouts per user role or context.
Aligns with the existing isHidden property already in PBIR at visual level, making it available for dynamic scenarios.
Why now
Conditional visibility is a frequent request feature in the community. Users of other Microsoft data platform solutions, such as Power Apps, are accustomed to having the ability to modify this property.
PBI developers already simulate this via workarounds (blank measures, bookmarks, overlaid shapes with managed transparency).
A native solution would make reports more dynamic, performant, and easier to maintain.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.