Build, check, then look.
Where does the validator run?
A change goes through seven steps, from idea to commit. The runs at one of them.
When should it run?
Put the loop in order
Tap the steps in the order they happen. The are where the agent waits for you.
Start with the first step.
The seed is the ground truth
Power BI Desktop writes each setting in its own way: property names, nesting, even punctuation. An agent guessing that format will sometimes guess wrong, and Desktop may refuse to open the report.
So a new setting is always made by hand in a small seed project first. Desktop writes it; the agent reads how Desktop wrote it and copies that. The seed is the . The validator then checks the main project against the spec, and some of its checks compare with the seed directly, like "needs textWrap as the seed writes it".
Four slips
The agent says: the seed hasn't changed since last time. But you just set the option.
The validator passes, but every tile's explanation tooltip is blank in Desktop.
You tried a new setting in the main project to see what it does, liked it, and saved.
Early in a project, only the model exists. The validator fails: pages missing.
Three things to keep
- 1The validator runs right after every build, before you spend time in Desktop.
- 2The agent stops twice: after proposing and after building. Those are yours.
- 3The seed is the . New settings start there, never in the main project.