Secrets of the Power BI report metadata - how it's possible to do more with Power BI reports than what the UI says or allows... why this is interesting, but also a problem. Link below...

Power BI needs a native Vega visual. Everything under the sun is pointing in that direction. The visuals are holding so much potential back right now.

I've been using the Fabric CLI a lot. Reflecting on it, I honestly think this is the most impactful feature for me from Fabric OR Power BI in recent years. I really do mean that. If you want an introduction to the Fabric CLI, I've written about it here: tabulareditor.com/blog/agent… Since I discovered the Fabric CLI, I find that I'm using it daily. TBH, I don't think I've EVER used ANY Power BI feature daily. To be clear, I don't execute commands most of the time; I give it to coding agents (I favor Claude Code) who do it for me. Incrementally over the months I've built up context files and examples, and compiled those in a few skills. Here's a few examples of things I've done with it, just in my own tenant: 1. I got a notification that a model refresh failed. I was at a conference and I needed that model for a demo, but I didn't have time to look into it. I just sent Claude Code after it using the Fabric CLI, asking to inspect the refresh history, model, notebooks, and data to figure out the issue. In a few minutes it crawled through the workspace and found the issue in one of the notebooks, fixed it, and then re-ran each notebook in sequence and refreshed the model, confirming if the refresh succeeded and querying it to validate. 2. I saw my Fabric Trial ticking down to 3 days and realized I needed to migrate all my trial workspaces. I can't automate this deterministically because each workspace needs a separate human decision: migrate to PPU, migrate to F SKU, migrate to Pro, or archive and delete. So I created a re-usable prompt and with a few parallel agents went through and did it in 20 minutes. I wrote about that here: lnkd.in/eufDkMkh -- my trial did get renewed though :P 3. I use it to facilitate CI/CD during agentic report development. This is something I've shared briefly ( lnkd.in/eqBTRDCx ) and started documenting in a longer video and article, but illness and injury in the last month has kept me from finishing it... IYKYK. Of course the Fabric CLI is also amazing for deterministic automation scenarios too, which many have blogged about like Peer Grønnerup ( lnkd.in/e-vJK52X ) and Kevin C. ( lnkd.in/ek4YUYiR ) If you were to tell me last year that 2025 was the year I'd fall in love with the command-line, I'd have laughed at you. "I'm a designer! I practically live in Figma and Excalidraw." And yet, here we are -- Claude Code and the Fabric CLI changed everything, for me. That's pretty cool.

Being able to refresh the tables like this is very convenient and much faster than "the old way" -- I find I'm already using it a lot.

Visual studio code and VS code extension for Power BI developers... in simple terms. This article explains the basics of why VS Code is a must-use for Power BI... even if you're not technical. From source control to extensions like Fabric Studio and AI tools... (Link Below)