pbi-cli/marketing/linkedin-posts/19-release-vibe-bi-comments.md
MinaSaad1 62680dd060 feat: v3.10.3 - opt-in Claude integration, dual-license DLL attribution, new pbi-cli entry point
## Claude Code integration now fully opt-in (Fix 3)
- `pbi connect` no longer writes to ~/.claude/ automatically
- New `pbi-cli` entry point: `pbi-cli skills install/uninstall/list`
- `pbi-cli skills install` shows exact paths before writing and requires y/N confirmation
- `pbi connect` prints a one-line tip if skills are not yet installed
- `pbi skills` subgroup removed from the `pbi` entry point

## DLL licensing compliance (Fix 1)
- pyproject.toml updated to PEP 639 SPDX dual expression:
  MIT AND LicenseRef-Microsoft-AS-Client-Libraries
- license-files declaration: LICENSE, THIRD_PARTY_LICENSES.md, NOTICE
- THIRD_PARTY_LICENSES.md: full verbatim MS Analysis Services Client Libraries EULA
- NOTICE: short-form attribution for wheel redistribution
- src/pbi_cli/dlls/README.md: in-directory sentinel for the MS DLLs
- setuptools requirement bumped to >=77.0 for PEP 639 support

## SECURITY.md rewrite (Fix 2)
- Supported versions table updated to 3.10.x
- Architecture section: no MCP server, no subprocess, direct pythonnet interop
- Global Configuration Modifications section updated to reflect opt-in model
- Bundled Binaries section references THIRD_PARTY_LICENSES.md

## Documentation
- README.md, README.pypi.md: corrected 3-step setup flow
- CHANGELOG.md: [3.10.3] entry
- CONTRIBUTING.md: pbi skills -> pbi-cli skills
- All 7 semantic model SKILL.md files: prerequisites updated to 3-step flow
- New SVG/PNG marketing and documentation assets
2026-04-05 20:37:05 +02:00

3.6 KiB
Raw Blame History


Comment 1 — Report Layer Overview

Here's the new 𝗥𝗲𝗽𝗼𝗿𝘁 𝗟𝗮𝘆𝗲𝗿 at a glance.

32 visual types, data binding, themes, and filters. All from the terminal.

No connection needed. It reads and writes PBIR JSON directly, auto-syncs with Desktop, and supports bulk operations.

One command to add a chart. One command to bind data. One command to apply your brand theme.


Comment 2 — 32 Visual Types

𝟯𝟮 𝘃𝗶𝘀𝘂𝗮𝗹 𝘁𝘆𝗽𝗲𝘀 you can add from one command.

Bar, line, column, area, scatter, combo, donut, waterfall, treemap, funnel. Cards, KPIs, gauges. Tables and matrices. Slicers for every use case. Azure Maps. Even decorative elements like shapes, images, and textboxes.

pbi visual add --type bar --page overview --name my_chart

That's it. Claude picks the right type, you describe what you need.


Comment 3 — Build a Report in 6 Steps

Full report from an empty folder in 𝟲 𝘀𝘁𝗲𝗽𝘀:

  1. Scaffold the project
  2. Add pages
  3. Add visuals
  4. Bind data
  5. Apply theme
  6. Validate

All steps work offline on PBIR files. Desktop auto-syncs when it's open. You can chain these in a single prompt and Claude handles the sequence.


Comment 4 — Desktop Auto-Sync

The part that makes this actually usable: 𝗗𝗲𝘀𝗸𝘁𝗼𝗽 𝗔𝘂𝘁𝗼-𝗦𝘆𝗻𝗰.

CLI writes PBIR files, takes a snapshot of your modeling work, then reopens Desktop with everything intact. Both layers preserved.

No more closing Desktop manually. No risk of losing unsaved model changes. It just works.


Comment 5 — Just Ask Claude

This is what it actually looks like in practice.

"Add a bar chart showing revenue by region to the overview page, and apply our corporate brand theme."

Claude runs the commands: adds the visual, binds the data, applies the theme, syncs Desktop. Then you say "filter it to top 10 regions" and it adds a TopN filter.

No drag-and-drop. No manual binding. Just describe what you want on the page.


Comment 6 — Two Layers, One CLI

The full picture: 𝗠𝗼𝗱𝗲𝗹𝗶𝗻𝗴 + 𝗥𝗲𝗽𝗼𝗿𝘁𝗶𝗻𝗴 side by side.

Semantic Model Layer uses live .NET interop for measures, tables, relationships, DAX. Report Layer uses PBIR file operations for visuals, pages, themes, filters.

7 Claude skills for modeling. 5 for reporting. 27 command groups. 125+ subcommands total.


Comment 7 — Architecture

How the dual-layer architecture works under the hood.

Modeling side: TMDL export/import, DAX engine, schema control. All through direct .NET TOM interop.

Reporting side: Visual builder, data binding, theme engine. All through PBIR JSON file operations.

One CLI bridges both. Claude picks the right layer automatically based on your request.


Comment 8 — Command Showcase

Side-by-side command showcase for both layers.

𝗠𝗼𝗱𝗲𝗹𝗶𝗻𝗴: model export, dax run, add-measure, table list, relationship list, model import.

𝗥𝗲𝗽𝗼𝗿𝘁𝗶𝗻𝗴: add-visual, bind-data, add-page, list-visuals, update-theme, export.

30+ commands across both layers. AI-native from the start.

GitHub: https://github.com/MinaSaad1/pbi-cli