| name | Power BI Visuals |
| description | Add, configure, bind data to, and bulk-manage visuals on Power BI PBIR report pages using pbi-cli. Invoke this skill whenever the user mentions "add a chart", "bar chart", "line chart", "card", "KPI", "gauge", "scatter", "table visual", "matrix", "slicer", "combo chart", "bind data", "visual type", "visual layout", "resize visuals", "bulk update visuals", "bulk delete", "visual calculations", or wants to place, move, bind, or remove any visual on a report page. Also invoke when the user asks what visual types are supported or how to connect a visual to their data model.
|
| tools | pbi-cli |
Power BI Visuals Skill
Create and manage visuals on PBIR report pages. No Power BI Desktop connection
is needed -- these commands operate directly on JSON files.
Adding Visuals
pbi visual add --page page_abc123 --type bar
pbi visual add --page page_abc123 --type card --name "Revenue Card"
pbi visual add --page page_abc123 --type scatter \
--x 50 --y 400 --width 600 --height 350
pbi visual add --page page_abc123 --type combo --name sales_combo
Each visual is created as a folder with a visual.json file inside the page's
visuals/ directory. The template includes the correct schema URL and queryState
roles for the chosen type.
Prerequisite: Measures Must Exist in the Semantic Model
visual bind writes field references into the visual JSON. It does not
create measures — it only records that a measure should exist. If the measure
is missing from the TMDL, every visual bound to it will show an error in Desktop.
Before binding any visual to a measure, verify the measure exists:
pbi connect
pbi measure create "Total Revenue" -e "SUM(Fact_Sales[Total_Revenue])" -t Fact_Sales
After adding measures directly to a TMDL file (without pbi connect):
close and reopen the .pbip file in Power BI Desktop. Desktop only reads TMDL
on file open — it does not hot-reload TMDL changes made on disk.
Checklist before opening Desktop:
- Every
--field, --value, --indicator reference points to a real measure or column in the TMDL
- Table names match exactly (case-sensitive in PBIR):
"Fact_Sales" ≠ "fact_sales"
- Measure names match exactly:
"Total Revenue" ≠ "Total_Revenue"
Binding Data
Visuals start empty. Use visual bind with Table[Column] notation to connect
them to your semantic model. The bind options vary by visual type -- see the
type table below.
pbi visual bind mybar --page p1 \
--category "Geography[Region]" --value "Sales[Revenue]"
pbi visual bind mycard --page p1 --field "Sales[Total Revenue]"
pbi visual bind mymatrix --page p1 \
--row "Product[Category]" --value "Sales[Amount]" --value "Sales[Quantity]"
pbi visual bind myscatter --page p1 \
--x "Sales[Quantity]" --y "Sales[Revenue]" --detail "Product[Name]"
pbi visual bind mycombo --page p1 \
--category "Calendar[Month]" --column "Sales[Revenue]" --line "Sales[Margin]"
pbi visual bind mykpi --page p1 \
--indicator "Sales[Revenue]" --goal "Sales[Target]" --trend "Calendar[Date]"
pbi visual bind mygauge --page p1 \
--value "Sales[Revenue]" --max "Sales[Target]"
Binding uses ROLE_ALIASES to translate friendly names like --value into the PBIR
role name (e.g. Y, Values, Data). Measure vs Column is inferred from the role:
value/indicator/goal/max roles create Measure references, category/row/detail roles
create Column references. Override with --measure flag if needed.
Inspecting and Updating
pbi visual list --page page_abc123
pbi visual get visual_def456 --page page_abc123
pbi visual update vis1 --page p1 --width 600 --height 400
pbi visual update vis1 --page p1 --x 100 --y 200
pbi visual update vis1 --page p1 --hidden
pbi visual update vis1 --page p1 --visible
pbi visual delete visual_def456 --page page_abc123
Container Properties
Set border, background, or title on the visual container itself:
pbi visual set-container vis1 --page p1 --background "#F0F0F0"
pbi visual set-container vis1 --page p1 --border-color "#CCCCCC" --border-width 2
pbi visual set-container vis1 --page p1 --title "Sales by Region"
Visual Calculations
Add DAX calculations that run inside the visual scope:
pbi visual calc-add vis1 --page p1 --role Values \
--name "RunningTotal" --expression "RUNNINGSUM([Revenue])"
pbi visual calc-list vis1 --page p1
pbi visual calc-delete vis1 --page p1 --name "RunningTotal"
Bulk Operations
Operate on many visuals at once by filtering with --type or --name-pattern:
pbi visual where --page overview --type barChart
pbi visual where --page overview --type kpi --y-min 300
pbi visual bulk-bind --page overview --type barChart \
--category "Date[Month]" --value "Sales[Revenue]"
pbi visual bulk-update --page overview --type kpi --width 250 --height 120
pbi visual bulk-update --page overview --name-pattern "Temp_*" --hidden
pbi visual bulk-delete --page overview --name-pattern "Placeholder_*"
Filter options for where, bulk-bind, bulk-update, bulk-delete:
--type -- PBIR visual type or alias (e.g. barChart, bar)
--name-pattern -- fnmatch glob on visual name (e.g. Chart_*)
--x-min, --x-max, --y-min, --y-max -- position bounds (pixels)
All bulk commands require at least --type or --name-pattern to prevent
accidental mass operations.
Supported Visual Types (32)
Charts
| Alias | PBIR Type | Bind Options |
|---|
| bar | barChart | --category, --value, --legend |
| line | lineChart | --category, --value, --legend |
| column | columnChart | --category, --value, --legend |
| area | areaChart | --category, --value, --legend |
| ribbon | ribbonChart | --category, --value, --legend |
| waterfall | waterfallChart | --category, --value, --breakdown |
| stacked_bar | stackedBarChart | --category, --value, --legend |
| clustered_bar | clusteredBarChart | --category, --value, --legend |
| clustered_column | clusteredColumnChart | --category, --value, --legend |
| scatter | scatterChart | --x, --y, --detail, --size, --legend |
| funnel | funnelChart | --category, --value |
| combo | lineStackedColumnComboChart | --category, --column, --line, --legend |
| donut / pie | donutChart | --category, --value, --legend |
| treemap | treemap | --category, --value |
Cards and KPIs
| Alias | PBIR Type | Bind Options |
|---|
| card | card | --field |
| card_visual | cardVisual | --field (modern card) |
| card_new | cardNew | --field |
| multi_row_card | multiRowCard | --field |
| kpi | kpi | --indicator, --goal, --trend |
| gauge | gauge | --value, --max / --target |
Tables
| Alias | PBIR Type | Bind Options |
|---|
| table | tableEx | --value |
| matrix | pivotTable | --row, --value, --column |
Slicers
| Alias | PBIR Type | Bind Options |
|---|
| slicer | slicer | --field |
| text_slicer | textSlicer | --field |
| list_slicer | listSlicer | --field |
| advanced_slicer | advancedSlicerVisual | --field (tile/image slicer) |
Maps
| Alias | PBIR Type | Bind Options |
|---|
| azure_map / map | azureMap | --category, --size |
Decorative and Navigation
| Alias | PBIR Type | Bind Options |
|---|
| action_button | actionButton | (no data binding) |
| image | image | (no data binding) |
| shape | shape | (no data binding) |
| textbox | textbox | (no data binding) |
| page_navigator | pageNavigator | (no data binding) |
Suppressing Auto-Sync (--no-sync)
By default, every write command automatically syncs Power BI Desktop. When
adding or binding many visuals in sequence, Desktop reloads after each one.
Use --no-sync on the visual command group to batch all changes, then call
pbi report reload once at the end:
pbi visual --no-sync add --page overview --type card --name rev_card
pbi visual --no-sync bind rev_card --page overview --field "Sales[Total Revenue]"
pbi visual --no-sync add --page overview --type bar --name sales_bar
pbi visual --no-sync bind sales_bar --page overview --category "Product[Category]" --value "Sales[Revenue]"
pbi report reload
JSON Output
All commands support --json for agent consumption:
pbi --json visual list --page overview
pbi --json visual get vis1 --page overview
pbi --json visual where --page overview --type barChart