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