Enable Smart Narrative Visual to Render Basic Markdown/HTML from DAX Measures for Rich Text Format
Business Problem:
As finance and analytics professionals, we rely heavily on the Smart Narrative visual in Power BI to communicate data-driven insights through dynamic textual explanations. These narratives often describe performance variations, root-cause drivers, and hierarchical breakdowns of financial KPIs — such as Volume/Mix effects by Business Unit, Region, and Sub-region.
However, the current capabilities of the Smart Narrative visual impose a significant limitation:
While DAX measures can programmatically construct and return rich, multi-layered narratives, the visual renders this content as plain text, without supporting inline formatting within those dynamically generated strings.
For example, if a DAX measure generates the following text:
"Impact for " & [BusinessUnitName] & " was " & FORMAT([Variance], "$#,0 M")
There is currently no way to render just [BusinessUnitName] in bold, or to apply italics, underline, or other formatting inline within the same dynamic measure. The formatting options offered by the Smart Narrative editor apply only at the visual or field level, not inside concatenated or computed parts of a string.
This severely limits the usability and impact of the narrative for end users, especially in reports where quick scannability, visual emphasis, and clarity are critical — such as executive dashboards or financial briefings.
Proposed Feature Enhancement:
We propose that the Smart Narrative visual be enhanced to recognize and render a minimal subset of Markdown or basic HTML syntax embedded in DAX-generated strings. This would allow developers to apply text formatting inline directly within DAX logic.
Suggested Supported Elements (Initial Scope):
Bold:
**text** (Markdown) or <b>text</b> (HTML)Italics:
*text* (Markdown) or <i>text</i> (HTML)Underline (if feasible):
<u>text</u>Line breaks:
UNICHAR(10) (already supported – retain current behavior)
"Impact for **" & [BusinessUnitName] & "** was " & FORMAT([Variance], "$#,0 M")
When rendered, the Business Unit name would appear in bold, improving readability and enabling clear emphasis.
Business Value and Benefits:
✔ Improved Readability:
Critical drivers and entities (e.g., BUs, KPIs) can be emphasized directly in the narrative, making it easier to interpret dense information.
✔ Dynamic Emphasis:
Formatting could be conditionally applied within DAX (e.g., highlight only items exceeding thresholds).
✔ Increased Developer Efficiency:
Reduces the need for workarounds like manually breaking narratives into multiple fields to simulate formatting.
✔ Better Stakeholder Engagement:
Narratives with better visual hierarchy enhance user experience, supporting executive-level storytelling with minimal effort.
Conclusion:
This enhancement would significantly expand the flexibility and effectiveness of the Smart Narrative visual in enterprise scenarios — especially for finance and operations teams that depend on clear, dynamic, and expressive storytelling directly from DAX logic. We believe this would align well with the vision of making Power BI a more intelligent, communicative, and end-user-friendly analytics platform.
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_v11 minutes agoCommunity ChampionNew604Views11likes2CommentsSemantic 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_v7 hours agoCommunity ChampionNew11Views1like0CommentsBulk 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 ...vishal14019711 hours agoFrequent VisitorNew6Views0likes0Comments