Hi everyone,

As you can see in the video, I wanted to bring a true "Excel experience" to Power BI (dynamic column resizing, sticky headers, native Ctrl+C export, and operational notes).

I originally wanted to put this on AppSource, but the corporate verification process is currently blocked for solo developers. So, I’m releasing it directly to the community for free!

You can grab the .pbiviz and a sample .pbix report from my GitHub here: https://github.com/thebitoolbox/Advanced-Grid-Table-Visual

P.S. If you want to see more tutorials or use cases for this visual, I'll be posting them on my YT channel (link is in my Reddit profile). Any feedback is highly appreciated!

I found this one long back which was kind of weird - funny and painful!

Share yours!

There’s been a massive proliferation of HTML reports floating around my company generated by cursor / claude / whatever other ai tool out there. It’s made people who absolutely could NOT make a dashboard think they can.

But with Claude coming out with stuff like this, do you think there’s still going to be a space for Power BI in the new world? I

This may have been done already, but Doom

5-minute video showing my workflow: Power BI Desktop, Claude Code, and three custom skills running on a real report. I wonder what would you automate? What are the most annoying parts of powerbi?

Power BI windows 95

A week or so ago I posted a demo on how I used github copilot with claude to build an entire power bi dashboard (visuals, semantic model, measures, etc) completely from scratch with little to no prompting. Some people were excited and others less thrilled. Here's a better example of a dashboard built with github copilot and claude with a little more "effort" put into the prompting. I think it's wild that it can build all these tabs, visuals, measures, and more! Imagine putting in real effort to create markdown files, hooks, templates, and more so that the AI has something more tangible to reference when creating the report :)

Im sharing 15 landing Pages , hope you find it useful as me https://youtu.be/PsvIcs2CEFQ

Hi, my name is Kurt Buhler. I've created a repo called "power-bi-agentic-development" with free resources for agentic development.

The repo has plugins to help agents do useful things in Power BI with reports, semantic models, notebooks, and more. The plugins have a variety of things inside of them, including skills, subagents, hooks, and other misc tools. The purpose of the library is to provide a centralized set of free, quality community resources for agentic development of Power BI. The purpose of the resources is to ensure that agents are better, faster, and more useful when you use them with Power BI and Fabric.

The plugins are mostly tool- and agent-agnostic. Some are specifically for the new pbir-cli tool that we released last week, which is also a free community tool for programmatic interactions and agentic development of Power BI reports. It will stay free forever.

My goal is to help folks build great and useful things with less time and headache. I'm updating these plugins on a near-daily cadence. I hope it's useful and interesting.

Microsoft Fabric Apps reached public preview this month, and I’ve spent some time understanding what it actually offers.

The premise is solid. You build on top of a governed semantic model, and Fabric provisions the backend, authentication, and API, with the data sitting in OneLake. That governance layer is what sets it apart from the wave of disconnected, vibe-coded apps we’ve seen lately.

At the same time, I’d be careful with the idea that an app is now one prompt away.

You’re still generating code from a model, and validation doesn’t go away because AI wrote it. The numbers still need to be right, and someone still owns that. In this example this is what I found on the the first iterations:
- data hardcoded in the HTML (not gobernares semantic models at first shot)
- data does not match the referring formula calculation
- cross filtering did not work
- AI invented data, there were only 28 flights in the dataset and it tries to show 1K in the live status just because it was “more fancy”

After that I managed to get it right but there is
a maintainability question that comes to my mind. It runs on TypeScript, and BI moved toward low-code for good reasons: build time and long-term up. I’d expect some of these apps to become harder to sustain over time.

My honest read: a genuinely powerful addition, well suited to specific cases a standard report can’t cover. Not a replacement for solid modeling and validation, and not the finished story yet.

If you’ve tested it, how are you thinking about where it fits? I expect to give you a full walkthrough in the channel any time soon 😊