Three in the loop
❤️ 3⚡ 0 About
Lesson 3 of 7

Seed first

Before the agent writes a new setting anywhere, you set it once by hand in the seed, a small report kept for examples. Here's why, and the day it went wrong.

1Guess first

You want word wrap on the card titles. How should the agent learn how Desktop writes that setting?

That small report is the : kept only for examples. The real report never gets a test change saved into it.

2The seed routine

First, make sure you're in the right window. Both projects look the same inside Desktop.

▣Seed- Power BI Desktop

Put the seed routine in order.

3The save that didn't land

A real one. You set the option, pressed Ctrl+S, told the agent. It came back with:

> Compared Seed.Report against the last commit. No changes found. The seed hasn't changed since 18 September.
NameDate modified
📁 Seed.Report18/09 16:42

What happened?

4One setting, one visual

In time the seed became a catalogue: one setting per visual, each with a code, and a subtitle giving its Format pane path.

S07Outer padding
General > Properties > Padding
S12Card inner margin
path in its subtitle
S16Title text wrap
General > Title > Text wrap
S35Tooltip from a measure
path in its subtitle

Why only one setting per visual?

Lesson complete

⚡ 0 XP❤️ 3 left
Next: Propose, then wait