Field Notes
What I learn running Power BI and Fabric with agents on my own systems, written down while it is fresh. The error guides give the symptom, the exact message where I kept it, the cause, the fix, and how I know. New notes are in the RSS feed.
Nothing matches that. Try a shorter word.
Notes 7
- Context Transition, Explained with Three Bugs I Wrote
Three real DAX mistakes from this site, each a different side of context transition and filter arguments, with the broken version, why it broke, and the fix.
- How This Site Tests Its Own DAX
Every DAX block here is linted on each build, every analysis number is computed from the demo CSVs, and the tests check identities, not snapshots. What that caught.
- Review a Power BI Release Before It Ships
A short release review for a semantic model saved as a TMDL project: compare it with production, read the checks, and keep a Markdown dictionary in git so the next diff is readable.
- Your Agent Transcripts May Be Deleted After 30 Days
The default cleanup setting removed my personal agent history. What I changed, and the append-only backup and monthly restore drill I put behind it.
- Don’t Accept ‘Done’ from an Agent Without a Quoted Source
An agent’s ‘done’ only tells you what it believes happened. The rule I enforce: no quote and source, no done, plus read-only review passes when being wrong is expensive.
- Guard Rails for Agents That Work Near Production
A guard hook, a kill switch, a headless launcher with caps, and a serial-only refresh rule: how I keep agents from doing damage in my home lab, and why to start in shadow mode.
- Routing Agent Work by Model Tier, and Red-Teaming My Own Automation
A task router that sends each job to the smallest model that can close it, plus a red-team unit that found a code-execution hole in my self-updating routine.
Error Guides 9
- Fabric Git Says “Can’t fetch branches”: Check the Tenant Setting
Connecting a workspace to GitHub failed on a new tenant until an admin enabled a tenant setting that is easy to miss.
- Direct Lake Relationship Skipped Because the Key Column Is Double
A fact table key landed in Delta as Double, so the relationship was skipped. How I changed the column type from TMDL view and got the relationship active.
- Direct Lake: “relationship needs to be recalculated” Is a Refresh You Forgot
After adding relationships to a Direct Lake model, queries fail until you reframe the model with a refresh.
- A Freshly Git-Deployed Power BI Model Won’t Refresh
After deploying an import model from Git into Fabric, refresh does nothing until you set the data source credential and re-enable scheduled refresh.
- TMDL InvalidLineType: A Doc Comment Followed by a Blank Line
In a TMDL file, /// doc comments followed by a blank line produce an InvalidLineType parse error. What to look for and what to change.
- PBIR Report Won’t Import into Fabric: Missing definition/version.json
A generated PBIR report failed to import because definition/version.json and two report.json fields were missing. What each one needs to contain.
- Notebook saveAsTable Fails: The Default Lakehouse Isn’t Attached
A Fabric notebook that writes Delta tables errors if you run it before attaching a lakehouse. The set-default option only appears after you add one.
- TMDL View: One Command per Apply
Pasting 21 separate createOrReplace commands into TMDL view does not work. Put the relationships under one command.
- Fabric Git Deploy Fails with ‘Unable to finish metadata synchronization’
A shared M function expression in a TMDL model broke deployment from Git. Inlining the M into each partition fixed it.