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

The FabCon + SQLCon recap series starts April 14th at 8am Pacific. If you’re tracking where AI is going inside Fabric, this first session is a can't miss. Register now

Add Description field for Bookmarks in Power BI Desktop and PBIR Format

Problem Statement: Power BI bookmarks are powerful tools for creating interactive reports, but they lack proper documentation capabilities. Currently, when creating bookmarks in Power BI Desktop, there is no way to store contextual information about:

  • Purpose and intent (Why was this bookmark created?)
  • Business scenario (When should users apply it?)
  • Expected behavior (What should happen when activated?)
  • Visual impact scope (Which visuals are affected and how?)
  • Other

 

Current Limitation: Bookmark definitions in PBIR format store technical metadata configuration but provide no field for bookmark descriptions or business context. This creates significant challenges when inheriting reports or maintaining complex bookmark-driven applications. A significant number of elements can already be extracted from PBIR, but we lack the "why" behind bookmark creation and usage.

 

Proposed Solution: Add a new multi-line optional description field to the bookmark creation UI within Power BI Desktop. This description should also be stored in the PBIR format alongside existing technical properties.

 

Desired Implementation:

  • Add a description text box in the bookmark edit dialog in Power BI Desktop
  • Store the description in the PBIR bookmark JSON schema as a new property
  • Display descriptions in bookmark tooltips
  • Enable version control and collaboration through the existing PBIR source control capabilities

 

Business Value: This enhancement would increase self-documenting report capabilities in Power BI where business context is stored directly in the source system. Teams could understand bookmark intent, improving report maintainability, knowledge transfer, and user adoption. The integration with PBIR ensures documentation follows the same version control workflow as the report itself.

 

Expected Outcome: Organizations would have a complete definition of bookmarks, both technical and contextual, stored directly in PBIR. Since this data would exist in PBIR, it could be easily parsed in Visual Studio Code to obtain a clear, comprehensive, and automatic solution for documenting bookmarks without manual effort.

Status: New