I spent the last few weeks building DashPrompts, a tool that turns a spreadsheet + a plain-English prompt into a real Power BI project (.pbip) that you can play with on desktop. Most of the interesting bugs weren't in the AI layer -- but were in the compiler that turns a "shopping list" of charts and measures into the actual TMDL/report.json files Power BI Desktop expects. 3 of them stood out.
1. A syntactically invalid M-query that only fails once Power BI actually parses it
Every embedded-table dashboard I generated failed to open, with a cryptic M Engine error: Token ',' expected. The root cause: inside a type table [Col = type text, ...] ascription, you're already in type-expression context -- so writing type text again is a syntax error. It has to be bare text. Int64.Type was unaffected, which is why the error always pointed at the first text column and sent me down the wrong path for a while (I initially suspected scientific-notation number formatting instead).
2. A measure property that quietly requires a specific Analysis Services compatibility level
I wanted a stacked bar chart's segments to self-label with a dynamic, SELECTEDVALUE-based format string (formatStringDefinition in TMDL). It kept failing with "Invalid indentation," which sent me chasing whitespace bugs for two rounds. The real blocker: that property requires AS compatibility level 1601, and my template had it hardcoded at 1550 from months earlier. The error message had nothing to do with the actual cause.
3. A password-reset flow that pointed every real user at localhost
Not Power BI bug, but a consequential one: Supabase's Auth "Site URL" defaults to http://localhost:3000 and nobody had ever changed it after going live. The actual password-reset code in the frontend was correct -- it was passing the real production URL as redirectTo -- but Supabase silently falls back to the Site URL whenever the requested redirect isn't on an explicit allow-list. Every single real user hitting "forgot password" got bounced to a dead localhost link. Fixed by setting the real Site URL and adding the production domain to the Redirect URLs allow-list -- a two-minute fix once found, but a very real "check your platform defaults, not just your own code" lesson.
If you're building anything that compiles into a rigid file format (TMDL, OOXML, whatever), the lesson that sticks
: trust the real engine's error over your own first guess at the cause, and verify behavior against the actual schema/docs rather than pattern-matching from a similar-looking property.
Building this in public at dashprompts.com if anyone's curious about the rest of it.
Top comments (0)