SVG Visuals via DAX Measures (PBIR)
Use pbir for every report mutation. The pbir-format skill is read-only schema context.
If the CLI is unavailable or lacks an operation, stop and report the gap.
Generate inline SVG graphics using DAX measures that return SVG markup strings. These render as images in table, matrix, card, image, and slicer visuals. Store as extension measures in reportExtensions.json.
How It Works
- A DAX measure returns an SVG string prefixed with
data:image/svg+xml;utf8,
- The measure's
dataCategory is set to ImageUrl
- Power BI renders the SVG as an image in supported visuals
Supported Visuals
- Table (
tableEx): grid.imageHeight / grid.imageWidth -- references/svg-table-matrix.md
- Matrix (
pivotTable): same as table -- references/svg-table-matrix.md
- Image (
image): sourceType='imageData' + sourceField -- references/svg-image-visual.md
- Card/New (
cardVisual): callout.imageFX -- references/svg-card-slicer.md
- Slicer/New (
advancedSlicerVisual): header images -- references/svg-card-slicer.md
Workflow: Creating an SVG Measure
Step 0: Design and Preview
Before writing DAX, design the SVG visually:
- Query the model first -- use DAX Studio or Tabular Editor CLI to get actual values with the intended filter context. Use real numbers, not placeholders.
- Write static SVG to a temp file -- save to
/tmp/mockup.svg and open it in a browser to preview layout, colors, and proportions.
- Ask for feedback before converting to DAX -- iterating on static SVG is far easier than on DAX string concatenation.
- Colors must be hex codes with
# -- e.g., fill='#2B7A78'. Never use %23 URL encoding or named colors. Always hex.
Step 1: Create the Extension Measure
Create the extension measure in reportExtensions.json manually (see the pbir-format skill in the pbip plugin for JSON structure).
# Example using pbir_object_model (if available):
report.add_extension_measure(
table="Orders",
name="Sparkline SVG",
expression='''
VAR _Prefix = "data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 100 30'>"
VAR _Bar = "<rect x='0' y='0' width='50' height='30' fill='#2196F3'/>"
VAR _Suffix = "</svg>"
RETURN _Prefix & _Bar & _Suffix
''',
data_type="Text",
data_category="ImageUrl",
display_folder="SVG Charts",
)
report.save()
Step 1b: Review
Before presenting the measure to the user, dispatch the svg-reviewer agent to validate syntax and provide design feedback.
Step 2: Bind to a Visual
Extension measures use "Schema": "extension" in the SourceRef:
{
"field": {
"Measure": {
"Expression": {
"SourceRef": {"Schema": "extension", "Entity": "Orders"}
},
"Property": "Sparkline SVG"
}
}
}
For image visuals, bind the SVG measure through pbir add visual image --image; see
references/svg-image-visual.md.
Step 3: Validate
Validate with pbir validate "Report.Report" --all and inspect bindings with
pbir visuals bind "...Visual" --show.
Prefer UDF Libraries Over Custom DAX
Before writing a custom SVG measure from scratch, check whether an existing UDF library already provides the chart type:
- PowerofBI.IBCS (Andrzej Leszkiewicz) -- IBCS-compliant bar, column, waterfall, pin, small multiples, and P&L charts. Preferred for business reporting with AC/PY/BU/FC comparisons. Install from https://daxlib.org/package/PowerofBI.IBCS/
- DaxLib.SVG (Jake Duddy) -- general-purpose sparklines, bars, boxplots, heatmaps, jitter, violin, progress bars, pills. Install from https://daxlib.org/package/DaxLib.SVG/ -- source at https://github.com/daxlib/dev-daxlib-svg
- PowerBI MacGuyver Toolbox (Stepan Resl / Data Goblins) -- C# scripts that generate SVG measures via Tabular Editor
To check if a library is installed, look for functions/measures starting with PowerofBI.IBCS., Viz., Compound., or Element.. Only write custom SVG DAX when no library function covers the required visualization. See references/community-examples.md for full function listings and additional libraries.
Installing UDF libraries
UDF libraries are installed into the semantic model, not the report. Use one of these tools:
- Tabular Editor CLI (
te command) -- use the te-docs skill for guidance
- Power BI MCP server -- if available, use it to modify the model directly
connect-pbid skill -- connect to Power BI Desktop's local Analysis Services instance via TOM/PowerShell
tmdl skill -- edit TMDL files directly in a PBIP project (last resort)
DAX SVG Conventions
Measure Structure (VAR Pattern)
Every SVG measure must follow a strict VAR-based structure. Organize code into clearly separated regions:
SVG Measure =
-- CONFIG: Input fields and visual parameters
VAR _Actual = [Sales Amount]
VAR _Target = [Sales Target]
VAR _Scope = ALLSELECTED ( 'Product'[Category] )
-- CONFIG: Colors
VAR _BarColor = "#5B8DBE"
VAR _TargetColor = "#333333"
-- NORMALIZATION: Scale values to SVG coordinate space
VAR _AxisMax = CALCULATE( MAXX( _Scope, [Sales Amount] ), REMOVEFILTERS( 'Product'[Category] ) ) * 1.1
VAR _AxisRange = 100
VAR _ActualNormalized = DIVIDE( _Actual, _AxisMax ) * _AxisRange
-- SVG ELEMENTS: One VAR per visual element
VAR _SvgPrefix = "data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 100 25'>"
VAR _Sort = "<desc>" & FORMAT( _Actual, "000000000000" ) & "</desc>"
VAR _Bar = "<rect x='0' y='5' width='" & _ActualNormalized & "' height='15' fill='" & _BarColor & "'/>"
VAR _TargetLine = "<rect x='" & DIVIDE( _Target, _AxisMax ) * _AxisRange & "' y='2' width='2' height='21' fill='" & _TargetColor & "'/>"
VAR _SvgSuffix = "</svg>"
-- ASSEMBLY: Combine in rendering order (back to front)
VAR _SVG = _SvgPrefix & _Sort & _Bar & _TargetLine & _SvgSuffix
RETURN _SVG
Key conventions:
- CONFIG section first -- input measures, scope column, colors, font settings. Users change only this section.
- NORMALIZATION section -- scale raw values to SVG coordinate space (see below)
- SVG ELEMENTS -- one VAR per
<rect>, <circle>, <text>, <line>, etc.
- ASSEMBLY -- concatenate elements in document order (first = back layer, last = front)
<desc> sort trick -- embed FORMAT(_Actual, "000000000000") in a <desc> tag so the table/matrix can sort by the SVG column
Axis Normalization (Critical)
SVG coordinates must be normalized to a fixed range. Raw measure values (e.g., 1,234,567) cannot be used directly as pixel coordinates. The standard pattern:
-- 1. Define the SVG coordinate range
VAR _BarMin = 0 -- leftmost position (or offset for labels)
VAR _BarMax = 100 -- rightmost position
-- 2. Find the maximum value across all rows in the visual's filter context
VAR _Scope = ALLSELECTED( 'Table'[GroupColumn] )
VAR _MaxInScope = CALCULATE( MAXX( _Scope, [Measure] ), REMOVEFILTERS( 'Table'[GroupColumn] ) )
VAR _AxisMax = _MaxInScope * 1.1 -- 10% padding
-- 3. Normalize each value to the SVG range
VAR _AxisRange = _BarMax - _BarMin
VAR _Normalized = DIVIDE( _Actual, _AxisMax ) * _AxisRange
Use ALLSELECTED for the scope when the chart should respond to slicer context. Use ALL for a fixed axis across all filter contexts. The * 1.1 padding prevents bars from touching the edge.
HASONEVALUE Guard
Table/matrix SVG measures must guard against subtotal/total rows where multiple categories are in scope:
IF( HASONEVALUE( 'Table'[GroupColumn] ),
-- SVG code here
)
Without this guard, the measure evaluates on grand total rows with meaningless aggregated values.
Escaping and Color Rules
- Single quotes for SVG attributes -- avoids DAX double-quote escaping:
fill='#2196F3'
- Double quotes in DAX: escape as
"" (DAX convention)
viewBox for responsive scaling: viewBox='0 0 100 25'
xmlns required on <svg> element
- Hex colors with
# only -- e.g., fill='#2196F3'. %23 URL encoding causes errors in image visuals. Never use named colors.
- No JavaScript -- SVG must be purely declarative
SVG Coordinate System
- Y=0 is at the top -- invert values for charts:
_Height - _Value
- Use
viewBox with a 0-100 range for normalized coordinates
- Elements render in document order (first = back, last = front)
CONCATENATEX for Series Data
For sparklines and multi-point charts, build coordinate strings with CONCATENATEX:
VAR _Points = CONCATENATEX(
_SparklineTable,
[X] & "," & (100 - [Y]),
" ",
[Date], ASC
)
-- Produces: "0,80 10,60 20,40 30,20"
-- Use in: <polyline points='...'/>
Best Practices
- Check UDF libraries first -- use DaxLib.SVG or MacGuyver Toolbox functions before writing custom DAX
- VAR pattern mandatory -- one VAR per config value, one VAR per SVG element, assembly at the end
- Normalize all values -- raw measure values must be scaled to SVG coordinate range
- HASONEVALUE guard -- always guard against total/subtotal rows in table/matrix context; use
ISINSCOPE for nested hierarchy levels
<desc> sort trick -- embed formatted value in <desc> for sortable SVG columns
- Use
viewBox for responsive scaling instead of fixed width/height
- Round coordinates to integers for performance (shorter strings, cheaper FORMAT calls)
- Store as extension measures -- SVG measures don't belong in the semantic model
- Use
display_folder to organize SVG measures (e.g., "SVG Charts")
- Preview first -- save static SVG to
/tmp/, open in browser, iterate before writing DAX
- 32K character limit on the rendered SVG string per cell (not the DAX expression); see
references/svg-table-matrix.md for diagnosis and mitigation
- Pre-aggregate in model measures -- let the storage engine cache aggregations; the SVG measure maps numbers to coordinates only
- Hex colors only --
# directly, never %23 URL encoding
- Image visuals need no
query block -- only objects.image with sourceType='imageData' and sourceField
- Accessibility: every SVG encoding primary data needs adjacent readable columns and a dynamic alt-text measure; see
references/svg-accessibility.md
reportExtensions.json Format
{
"$schema": "https://developer.microsoft.com/json-schemas/fabric/item/report/definition/reportExtension/1.0.0/schema.json",
"name": "extension",
"entities": [{
"name": "ExistingTable",
"measures": [{
"name": "Sparkline SVG",
"dataType": "Text",
"dataCategory": "ImageUrl",
"expression": "...",
"displayFolder": "SVG Charts"
}]
}]
}
Limitations
- No interactivity -- SVG images are static (no hover, click, tooltip)
- No JavaScript -- inline scripts are stripped
- 32K character limit per rendered cell string (not the DAX expression);
CONCATENATEX over 30+ series points easily approaches this; prefer <polyline> over individual shapes, integer coordinates, and pre-aggregated series; see references/svg-table-matrix.md for full diagnosis
- Per-cell formula-engine cost -- each visible cell evaluates the string-building expression; push aggregations into model measures so SVG assembly is coordinate-mapping only
- Accessibility gap -- screen readers receive no per-cell data from an SVG URI; mitigate with adjacent readable columns and dynamic alt text; see
references/svg-accessibility.md
- Classic card (
card) does NOT support SVG -- use cardVisual instead
When to Use SVG Measures
SVG measures are the preferred choice for simple inline graphics embedded in tables, matrices, cards, and image visuals. Use SVG when you need:
- Sparklines, data bars, progress bars, or status indicators inside table/matrix cells
- KPI micro-charts in card visuals
- Lightweight visuals that don't require interactivity or complex data transforms
- No additional custom visual registration (works with native visuals)
Use Deneb instead for complex, interactive visualizations (cross-filtering, tooltips, hover states) or chart types that require extensive data transforms. Use Python/R instead for statistical analysis charts (distributions, regressions, correlations).
References
Community Examples and Libraries
references/community-examples.md -- Community SVG templates organized by target visual type (Table/Matrix, Image, Card), including DaxLib.SVG functions, Kerry Kolosko templates, and PowerBI MacGuyver Toolbox patterns
By Visual Type
references/svg-table-matrix.md -- Patterns for Table/Matrix: data bar, bullet chart, dumbbell, overlapping bars, lollipop, status pill, sparkline, bar sparkline, area sparkline, UDF patterns; axis normalization, sort trick, image size configuration, and per-cell performance guidance
references/svg-image-visual.md -- Patterns for Image visuals: KPI header, sparkline with endpoint, dashboard tile; sourceType binding, dynamic/conditional layout, responsive width guidance
references/svg-card-slicer.md -- Patterns for Card/Slicer: arrow indicator, mini gauge, mini donut, progress bar, narrative sentence; card binding via callout.imageFX
Accessibility
references/svg-accessibility.md -- Accessibility for SVG measures: adjacent readable columns, dynamic alt text, color-only encoding, contrast requirements, and severity guidance for audit findings
General
references/svg-elements.md -- SVG element reference (rect, circle, line, polyline, text, path, gradient, group)
Examples
Ready-to-use DAX measure expressions in examples/:
sparkline-measure.dax -- Line sparkline (polyline + CONCATENATEX)
progress-bar-measure.dax -- Conditional progress bar
dumbbell-chart-measure.dax -- Actual vs target dumbbell
bullet-chart-measure.dax -- Bullet chart with sentiment action dots
overlapping-bars-measure.dax -- Overlapping bars with variance label
boxplot-measure.dax -- Box-and-whisker plot (inspired by DaxLib.SVG)
ibcs-bar-measure.dax -- IBCS-compliant horizontal bar (inspired by avatorl)
jitter-plot-measure.dax -- Dot strip chart with jitter (inspired by DaxLib.SVG)
overlapping-bars-with-variance-measure.dax -- Overlapping bars with variance bar + arrow icon + % label (Kurt Buhler / Data Goblins)
lollipop-conditional-measure.dax -- Lollipop with scaled dot + auto-formatted label (Kurt Buhler / Data Goblins)
waterfall-measure.dax -- Waterfall with cumulative OFFSET positioning + connector lines (Kurt Buhler / Data Goblins)
status-pill-measure.dax -- Rounded pill badge with category color + text label (Kurt Buhler / Data Goblins)
Helper Libraries
| Library |
Author |
Key Features |
| DaxLib.SVG |
Jake Duddy |
UDF library: area, line, boxplot, heatmap, jitter, violin |
| PBI-Core-Visuals-SVG-HTML |
David Bacci |
Chips, tornado, gradient matrix, bar UDF |
| PowerBI MacGuyver Toolbox |
Stepan Resl / Data Goblins |
20+ bar, 14+ line, 24+ KPI templates |
| Dashboard Design UDF Library |
Dashboard-Design |
Target line bars, pill visuals |
| Kerry Kolosko Templates |
Kerry Kolosko |
Sparklines, data bars, KPI cards |
Related Skills
pbi-report-design -- Layout and design best practices
deneb-visuals -- Vega/Vega-Lite for complex interactive visualizations
python-visuals -- matplotlib/seaborn for statistical charts
r-visuals -- ggplot2 for statistical charts
pbir-format (pbip plugin) -- PBIR JSON format reference (extension measures, ImageUrl binding)
Source: data-goblin/power-bi-agentic-development → plugins/custom-visuals/skills/svg-visuals/SKILL.md
1---
2name: svg-visuals
3description: "SVG generation via DAX measures and extension measures with ImageUrl data category for inline visualizations in PBIR reports. Automatically invoke when the user mentions \"SVG visual\", \"DAX sparkline\", \"SVG measure\", \"inline graphics with DAX\", \"ImageUrl data category\", \"extension measure\", or asks to create any DAX-generated chart (progress bars, bullet charts, KPI indicators, data bars, gauges, donut charts, lollipop charts, dumbbell charts, status pills, overlapping bars, boxplots, IBCS bars, jitter plots, box-and-whisker charts)."
4category: frontend-and-design
5source_repo: data-goblin/power-bi-agentic-development
6source_path: "plugins/custom-visuals/skills/svg-visuals/SKILL.md"
7source_url: https://github.com/data-goblin/power-bi-agentic-development/blob/HEAD/plugins/custom-visuals/skills/svg-visuals/SKILL.md
8metadata:
9 source: https://skillmd.com/skills/data-goblin/svg-visuals
10---
11
12# SVG Visuals via DAX Measures (PBIR)
13
14> **Use `pbir` for every report mutation.** The `pbir-format` skill is read-only schema context.
15> If the CLI is unavailable or lacks an operation, stop and report the gap.
16
17Generate inline SVG graphics using DAX measures that return SVG markup strings. These render as images in table, matrix, card, image, and slicer visuals. Store as extension measures in `reportExtensions.json`.
18
19## How It Works
20
211. A DAX measure returns an SVG string prefixed with `data:image/svg+xml;utf8,`
222. The measure's `dataCategory` is set to `ImageUrl`
233. Power BI renders the SVG as an image in supported visuals
24
25## Supported Visuals
26
27- Table (`tableEx`): `grid.imageHeight` / `grid.imageWidth` -- `references/svg-table-matrix.md`
28- Matrix (`pivotTable`): same as table -- `references/svg-table-matrix.md`
29- Image (`image`): `sourceType='imageData'` + `sourceField` -- `references/svg-image-visual.md`
30- Card/New (`cardVisual`): `callout.imageFX` -- `references/svg-card-slicer.md`
31- Slicer/New (`advancedSlicerVisual`): header images -- `references/svg-card-slicer.md`
32
33## Workflow: Creating an SVG Measure
34
35### Step 0: Design and Preview
36
37Before writing DAX, design the SVG visually:
38
391. **Query the model first** -- use DAX Studio or Tabular Editor CLI to get actual values with the intended filter context. Use real numbers, not placeholders.
402. **Write static SVG to a temp file** -- save to `/tmp/mockup.svg` and `open` it in a browser to preview layout, colors, and proportions.
413. **Ask for feedback** before converting to DAX -- iterating on static SVG is far easier than on DAX string concatenation.
424. **Colors must be hex codes with `#`** -- e.g., `fill='#2B7A78'`. Never use `%23` URL encoding or named colors. Always hex.
43
44### Step 1: Create the Extension Measure
45
46Create the extension measure in `reportExtensions.json` manually (see the `pbir-format` skill in the pbip plugin for JSON structure).
47
48```python
49# Example using pbir_object_model (if available):
50report.add_extension_measure(
51 table="Orders",
52 name="Sparkline SVG",
53 expression='''
54 VAR _Prefix = "data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 100 30'>"
55 VAR _Bar = "<rect x='0' y='0' width='50' height='30' fill='#2196F3'/>"
56 VAR _Suffix = "</svg>"
57 RETURN _Prefix & _Bar & _Suffix
58 ''',
59 data_type="Text",
60 data_category="ImageUrl",
61 display_folder="SVG Charts",
62)
63report.save()
64```
65
66### Step 1b: Review
67
68Before presenting the measure to the user, dispatch the `svg-reviewer` agent to validate syntax and provide design feedback.
69
70### Step 2: Bind to a Visual
71
72Extension measures use `"Schema": "extension"` in the SourceRef:
73
74```json
75{
76 "field": {
77 "Measure": {
78 "Expression": {
79 "SourceRef": {"Schema": "extension", "Entity": "Orders"}
80 },
81 "Property": "Sparkline SVG"
82 }
83 }
84}
85```
86
87For **image visuals**, bind the SVG measure through `pbir add visual image --image`; see
88`references/svg-image-visual.md`.
89
90### Step 3: Validate
91
92Validate with `pbir validate "Report.Report" --all` and inspect bindings with
93`pbir visuals bind "...Visual" --show`.
94
95## Prefer UDF Libraries Over Custom DAX
96
97Before writing a custom SVG measure from scratch, check whether an existing UDF library already provides the chart type:
98
99- **PowerofBI.IBCS** (Andrzej Leszkiewicz) -- IBCS-compliant bar, column, waterfall, pin, small multiples, and P&L charts. Preferred for business reporting with AC/PY/BU/FC comparisons. Install from https://daxlib.org/package/PowerofBI.IBCS/
100- **DaxLib.SVG** (Jake Duddy) -- general-purpose sparklines, bars, boxplots, heatmaps, jitter, violin, progress bars, pills. Install from https://daxlib.org/package/DaxLib.SVG/ -- source at https://github.com/daxlib/dev-daxlib-svg
101- **PowerBI MacGuyver Toolbox** (Stepan Resl / Data Goblins) -- C# scripts that generate SVG measures via Tabular Editor
102
103To check if a library is installed, look for functions/measures starting with `PowerofBI.IBCS.`, `Viz.`, `Compound.`, or `Element.`. Only write custom SVG DAX when no library function covers the required visualization. See `references/community-examples.md` for full function listings and additional libraries.
104
105### Installing UDF libraries
106
107UDF libraries are installed into the semantic model, not the report. Use one of these tools:
108
109- **Tabular Editor CLI** (`te` command) -- use the `te-docs` skill for guidance
110- **Power BI MCP server** -- if available, use it to modify the model directly
111- **`connect-pbid` skill** -- connect to Power BI Desktop's local Analysis Services instance via TOM/PowerShell
112- **`tmdl` skill** -- edit TMDL files directly in a PBIP project (last resort)
113
114## DAX SVG Conventions
115
116### Measure Structure (VAR Pattern)
117
118Every SVG measure must follow a strict VAR-based structure. Organize code into clearly separated regions:
119
120```dax
121SVG Measure =
122-- CONFIG: Input fields and visual parameters
123VAR _Actual = [Sales Amount]
124VAR _Target = [Sales Target]
125VAR _Scope = ALLSELECTED ( 'Product'[Category] )
126
127-- CONFIG: Colors
128VAR _BarColor = "#5B8DBE"
129VAR _TargetColor = "#333333"
130
131-- NORMALIZATION: Scale values to SVG coordinate space
132VAR _AxisMax = CALCULATE( MAXX( _Scope, [Sales Amount] ), REMOVEFILTERS( 'Product'[Category] ) ) * 1.1
133VAR _AxisRange = 100
134VAR _ActualNormalized = DIVIDE( _Actual, _AxisMax ) * _AxisRange
135
136-- SVG ELEMENTS: One VAR per visual element
137VAR _SvgPrefix = "data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 100 25'>"
138VAR _Sort = "<desc>" & FORMAT( _Actual, "000000000000" ) & "</desc>"
139VAR _Bar = "<rect x='0' y='5' width='" & _ActualNormalized & "' height='15' fill='" & _BarColor & "'/>"
140VAR _TargetLine = "<rect x='" & DIVIDE( _Target, _AxisMax ) * _AxisRange & "' y='2' width='2' height='21' fill='" & _TargetColor & "'/>"
141VAR _SvgSuffix = "</svg>"
142
143-- ASSEMBLY: Combine in rendering order (back to front)
144VAR _SVG = _SvgPrefix & _Sort & _Bar & _TargetLine & _SvgSuffix
145
146RETURN _SVG
147```
148
149Key conventions:
150- **CONFIG section first** -- input measures, scope column, colors, font settings. Users change only this section.
151- **NORMALIZATION section** -- scale raw values to SVG coordinate space (see below)
152- **SVG ELEMENTS** -- one VAR per `<rect>`, `<circle>`, `<text>`, `<line>`, etc.
153- **ASSEMBLY** -- concatenate elements in document order (first = back layer, last = front)
154- **`<desc>` sort trick** -- embed `FORMAT(_Actual, "000000000000")` in a `<desc>` tag so the table/matrix can sort by the SVG column
155
156### Axis Normalization (Critical)
157
158SVG coordinates must be normalized to a fixed range. Raw measure values (e.g., 1,234,567) cannot be used directly as pixel coordinates. The standard pattern:
159
160```dax
161-- 1. Define the SVG coordinate range
162VAR _BarMin = 0 -- leftmost position (or offset for labels)
163VAR _BarMax = 100 -- rightmost position
164
165-- 2. Find the maximum value across all rows in the visual's filter context
166VAR _Scope = ALLSELECTED( 'Table'[GroupColumn] )
167VAR _MaxInScope = CALCULATE( MAXX( _Scope, [Measure] ), REMOVEFILTERS( 'Table'[GroupColumn] ) )
168VAR _AxisMax = _MaxInScope * 1.1 -- 10% padding
169
170-- 3. Normalize each value to the SVG range
171VAR _AxisRange = _BarMax - _BarMin
172VAR _Normalized = DIVIDE( _Actual, _AxisMax ) * _AxisRange
173```
174
175Use `ALLSELECTED` for the scope when the chart should respond to slicer context. Use `ALL` for a fixed axis across all filter contexts. The `* 1.1` padding prevents bars from touching the edge.
176
177### HASONEVALUE Guard
178
179Table/matrix SVG measures must guard against subtotal/total rows where multiple categories are in scope:
180
181```dax
182IF( HASONEVALUE( 'Table'[GroupColumn] ),
183 -- SVG code here
184)
185```
186
187Without this guard, the measure evaluates on grand total rows with meaningless aggregated values.
188
189### Escaping and Color Rules
190
191- **Single quotes for SVG attributes** -- avoids DAX double-quote escaping: `fill='#2196F3'`
192- **Double quotes in DAX**: escape as `""` (DAX convention)
193- **`viewBox`** for responsive scaling: `viewBox='0 0 100 25'`
194- **`xmlns`** required on `<svg>` element
195- **Hex colors with `#` only** -- e.g., `fill='#2196F3'`. `%23` URL encoding causes errors in image visuals. Never use named colors.
196- **No JavaScript** -- SVG must be purely declarative
197
198### SVG Coordinate System
199
200- Y=0 is at the **top** -- invert values for charts: `_Height - _Value`
201- Use `viewBox` with a 0-100 range for normalized coordinates
202- Elements render in document order (first = back, last = front)
203
204### CONCATENATEX for Series Data
205
206For sparklines and multi-point charts, build coordinate strings with CONCATENATEX:
207
208```dax
209VAR _Points = CONCATENATEX(
210 _SparklineTable,
211 [X] & "," & (100 - [Y]),
212 " ",
213 [Date], ASC
214)
215-- Produces: "0,80 10,60 20,40 30,20"
216-- Use in: <polyline points='...'/>
217```
218
219## Best Practices
220
221- Check UDF libraries first -- use DaxLib.SVG or MacGuyver Toolbox functions before writing custom DAX
222- VAR pattern mandatory -- one VAR per config value, one VAR per SVG element, assembly at the end
223- Normalize all values -- raw measure values must be scaled to SVG coordinate range
224- HASONEVALUE guard -- always guard against total/subtotal rows in table/matrix context; use `ISINSCOPE` for nested hierarchy levels
225- `<desc>` sort trick -- embed formatted value in `<desc>` for sortable SVG columns
226- Use `viewBox` for responsive scaling instead of fixed width/height
227- Round coordinates to integers for performance (shorter strings, cheaper FORMAT calls)
228- Store as extension measures -- SVG measures don't belong in the semantic model
229- Use `display_folder` to organize SVG measures (e.g., `"SVG Charts"`)
230- Preview first -- save static SVG to `/tmp/`, open in browser, iterate before writing DAX
231- 32K character limit on the rendered SVG string per cell (not the DAX expression); see `references/svg-table-matrix.md` for diagnosis and mitigation
232- Pre-aggregate in model measures -- let the storage engine cache aggregations; the SVG measure maps numbers to coordinates only
233- Hex colors only -- `#` directly, never `%23` URL encoding
234- Image visuals need no `query` block -- only `objects.image` with `sourceType='imageData'` and `sourceField`
235- Accessibility: every SVG encoding primary data needs adjacent readable columns and a dynamic alt-text measure; see `references/svg-accessibility.md`
236
237## reportExtensions.json Format
238
239```json
240{
241 "$schema": "https://developer.microsoft.com/json-schemas/fabric/item/report/definition/reportExtension/1.0.0/schema.json",
242 "name": "extension",
243 "entities": [{
244 "name": "ExistingTable",
245 "measures": [{
246 "name": "Sparkline SVG",
247 "dataType": "Text",
248 "dataCategory": "ImageUrl",
249 "expression": "...",
250 "displayFolder": "SVG Charts"
251 }]
252 }]
253}
254```
255
256## Limitations
257
258- No interactivity -- SVG images are static (no hover, click, tooltip)
259- No JavaScript -- inline scripts are stripped
260- 32K character limit per rendered cell string (not the DAX expression); `CONCATENATEX` over 30+ series points easily approaches this; prefer `<polyline>` over individual shapes, integer coordinates, and pre-aggregated series; see `references/svg-table-matrix.md` for full diagnosis
261- Per-cell formula-engine cost -- each visible cell evaluates the string-building expression; push aggregations into model measures so SVG assembly is coordinate-mapping only
262- Accessibility gap -- screen readers receive no per-cell data from an SVG URI; mitigate with adjacent readable columns and dynamic alt text; see `references/svg-accessibility.md`
263- Classic card (`card`) does NOT support SVG -- use `cardVisual` instead
264
265## When to Use SVG Measures
266
267SVG measures are the preferred choice for **simple inline graphics** embedded in tables, matrices, cards, and image visuals. Use SVG when you need:
268
269- Sparklines, data bars, progress bars, or status indicators inside table/matrix cells
270- KPI micro-charts in card visuals
271- Lightweight visuals that don't require interactivity or complex data transforms
272- No additional custom visual registration (works with native visuals)
273
274**Use Deneb instead** for complex, interactive visualizations (cross-filtering, tooltips, hover states) or chart types that require extensive data transforms. **Use Python/R instead** for statistical analysis charts (distributions, regressions, correlations).
275
276## References
277
278### Community Examples and Libraries
279
280- **`references/community-examples.md`** -- Community SVG templates organized by target visual type (Table/Matrix, Image, Card), including DaxLib.SVG functions, Kerry Kolosko templates, and PowerBI MacGuyver Toolbox patterns
281
282### By Visual Type
283
284- **`references/svg-table-matrix.md`** -- Patterns for Table/Matrix: data bar, bullet chart, dumbbell, overlapping bars, lollipop, status pill, sparkline, bar sparkline, area sparkline, UDF patterns; axis normalization, sort trick, image size configuration, and per-cell performance guidance
285- **`references/svg-image-visual.md`** -- Patterns for Image visuals: KPI header, sparkline with endpoint, dashboard tile; sourceType binding, dynamic/conditional layout, responsive width guidance
286- **`references/svg-card-slicer.md`** -- Patterns for Card/Slicer: arrow indicator, mini gauge, mini donut, progress bar, narrative sentence; card binding via `callout.imageFX`
287
288### Accessibility
289
290- **`references/svg-accessibility.md`** -- Accessibility for SVG measures: adjacent readable columns, dynamic alt text, color-only encoding, contrast requirements, and severity guidance for audit findings
291
292### General
293
294- **`references/svg-elements.md`** -- SVG element reference (rect, circle, line, polyline, text, path, gradient, group)
295
296### Examples
297
298Ready-to-use DAX measure expressions in `examples/`:
299- **`sparkline-measure.dax`** -- Line sparkline (polyline + CONCATENATEX)
300- **`progress-bar-measure.dax`** -- Conditional progress bar
301- **`dumbbell-chart-measure.dax`** -- Actual vs target dumbbell
302- **`bullet-chart-measure.dax`** -- Bullet chart with sentiment action dots
303- **`overlapping-bars-measure.dax`** -- Overlapping bars with variance label
304- **`boxplot-measure.dax`** -- Box-and-whisker plot (inspired by DaxLib.SVG)
305- **`ibcs-bar-measure.dax`** -- IBCS-compliant horizontal bar (inspired by avatorl)
306- **`jitter-plot-measure.dax`** -- Dot strip chart with jitter (inspired by DaxLib.SVG)
307- **`overlapping-bars-with-variance-measure.dax`** -- Overlapping bars with variance bar + arrow icon + % label (Kurt Buhler / Data Goblins)
308- **`lollipop-conditional-measure.dax`** -- Lollipop with scaled dot + auto-formatted label (Kurt Buhler / Data Goblins)
309- **`waterfall-measure.dax`** -- Waterfall with cumulative OFFSET positioning + connector lines (Kurt Buhler / Data Goblins)
310- **`status-pill-measure.dax`** -- Rounded pill badge with category color + text label (Kurt Buhler / Data Goblins)
311
312## Helper Libraries
313
314| Library | Author | Key Features |
315|---------|--------|--------------|
316| DaxLib.SVG | Jake Duddy | UDF library: area, line, boxplot, heatmap, jitter, violin |
317| PBI-Core-Visuals-SVG-HTML | David Bacci | Chips, tornado, gradient matrix, bar UDF |
318| PowerBI MacGuyver Toolbox | Stepan Resl / Data Goblins | 20+ bar, 14+ line, 24+ KPI templates |
319| Dashboard Design UDF Library | Dashboard-Design | Target line bars, pill visuals |
320| Kerry Kolosko Templates | Kerry Kolosko | Sparklines, data bars, KPI cards |
321
322## Related Skills
323
324- **`pbi-report-design`** -- Layout and design best practices
325- **`deneb-visuals`** -- Vega/Vega-Lite for complex interactive visualizations
326- **`python-visuals`** -- matplotlib/seaborn for statistical charts
327- **`r-visuals`** -- ggplot2 for statistical charts
328- **`pbir-format`** (pbip plugin) -- PBIR JSON format reference (extension measures, ImageUrl binding)
329
330---
331
332**Source:** [`data-goblin/power-bi-agentic-development`](https://github.com/data-goblin/power-bi-agentic-development) → `plugins/custom-visuals/skills/svg-visuals/SKILL.md`