pbi-cli/marketing/linkedin-posts/08-dax-debugging.md

<!-- Post 08 | Phase 3: Skill Deep Dives | Day 8 -->
<!-- Image: dax-debugging.png (Debug DAX Like Never Before) -->

Your YTD Revenue measure is returning blank. What do you do?

Most people start guessing. Comment out lines. Add variables. Stare at CALCULATE filters. Waste 45 minutes before finding it was a date table issue the whole time.

With 𝗽𝗯𝗶-𝗰𝗹𝗶, I told Claude: "My YTD Revenue measure returns blank. Can you investigate?"

Claude traced the problem like a senior developer would 🔍

- Checked the measure definition. Syntax was fine.
- Checked the DAX logic. TOTALYTD looked correct.
- Checked the Calendar table. Found it. The table wasn't 𝗺𝗮𝗿𝗸𝗲𝗱 𝗮𝘀 𝗮 𝗱𝗮𝘁𝗲 𝘁𝗮𝗯𝗹𝗲.
- Fixed it with one command. Measure started working immediately.

Systematic. Methodical. No guessing.

That's the difference. Claude doesn't just write DAX. It 𝗱𝗲𝗯𝘂𝗴𝘀 it. It reads your model structure, understands context, and traces root causes.

Stop guessing. Let Claude trace it. 🛠️

GitHub: https://github.com/MinaSaad1/pbi-cli
Learn more: mina-saad.com/pbi-cli

#PowerBI #DAX #Debugging #ClaudeCode #VIbeModeling #OpenSource #DataModeling #AI
-												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 18:37:05 +00:00
+								<!-- Post 08 | Phase 3: Skill Deep Dives | Day 8 -->
 								<!-- Image: dax-debugging.png (Debug DAX Like Never Before) -->
 								Your YTD Revenue measure is returning blank. What do you do?
 								Most people start guessing. Comment out lines. Add variables. Stare at CALCULATE filters. Waste 45 minutes before finding it was a date table issue the whole time.
 								With 𝗽𝗯𝗶-𝗰𝗹𝗶, I told Claude: "My YTD Revenue measure returns blank. Can you investigate?"
 								Claude traced the problem like a senior developer would 🔍
 								- Checked the measure definition. Syntax was fine.
 								- Checked the DAX logic. TOTALYTD looked correct.
 								- Checked the Calendar table. Found it. The table wasn't 𝗺𝗮𝗿𝗸𝗲𝗱 𝗮𝘀 𝗮 𝗱𝗮𝘁𝗲 𝘁𝗮𝗯𝗹𝗲.
 								- Fixed it with one command. Measure started working immediately.
 								Systematic. Methodical. No guessing.
 								That's the difference. Claude doesn't just write DAX. It 𝗱𝗲𝗯𝘂𝗴𝘀 it. It reads your model structure, understands context, and traces root causes.
 								Stop guessing. Let Claude trace it. 🛠️
 								GitHub: https://github.com/MinaSaad1/pbi-cli
 								Learn more: mina-saad.com/pbi-cli
 								#PowerBI #DAX #Debugging #ClaudeCode #VIbeModeling #OpenSource #DataModeling #AI