Model Properties
manage_model_properties lets the assistant read and update global model metadata. In practice, you use it to:
- Make the model self-documenting - add a description that says what this model is for, who owns it, and when it was last reviewed, so the next person who opens it does not have to guess.
- Set the default culture - control how numbers and dates are formatted (decimal separators, date formats) across the model.
- Discourage implicit measures - prevent report authors from accidentally dragging numeric columns into visuals and getting meaningless SUM/COUNT aggregations instead of your authored measures.
- Tag the model with governance metadata - add annotations like owner, support channel, PII flags, or certification status that tools and processes can read.
- Upgrade compatibility level - unlock newer engine features (irreversible, high impact - always checkpoint first).
You don’t need to know tool parameters-ask the LLM to propose minimal metadata changes and wait for confirmation before applying.
What to ask the LLM (quick prompts)
“Show current model properties and summarize anything that looks off.” “Update the model description to include: purpose, owner, primary audience, and last reviewed date. Don’t change anything else.” “Enable ‘discourage implicit measures’ and explain the impact.” “Add model annotations for owner/support contact and governance tags.” “Explain whether we should upgrade compatibility level and what risks it has. Don’t do it unless I confirm.”Common tasks (copy/paste prompts)
1) Make the model self-documenting
“Update the model description to include: purpose, owner, support channel, and last reviewed date. Keep it concise.”2) Set culture intentionally
“Set default model culture toen-US and explain what this affects (formatting, separators, etc.).”
3) Discourage implicit measures (recommended for governed models)
“Enable ‘discourage implicit measures’. Explain what users will see differently in reporting tools.”4) Add governance annotations
Annotations are key/value metadata on the model. Typical uses:
- ownership/contact (
owner,support_channel) - governance tags (
pii_present,certified,domain) - documentation links (runbooks)
Prompt:
“Add model annotations: owner, support channel, andpii_present=true.”
Compatibility level upgrades (high impact)
Compatibility upgrades can be irreversible and can affect which versions of Power BI/tools can open the model.
Best practice:
- take a backup checkpoint (or save a copy of the PBIX) before upgrading,
- only upgrade when explicitly requested,
- ask for a clear “why” and “what changes”.
Prompt:
“Explain the impact of upgrading compatibility level and ask me to confirm. Do not proceed without confirmation.”Risk & governance notes (read this once)
Locked-down environments (mode behavior)
| Mode | Availability |
|---|---|
| Full mode | AvailableAvailable |
| Read-only mode | Not availableNot available |
| Browse-only mode | Not availableNot available |
Notes: Authoring (writes); compatibility upgrades are high-impact and confirm-gated.
Fallback when locked down:
“Uselist_model to show basic model properties (name/description/culture/etc.) and propose the property updates I should apply manually.”
Troubleshooting
You’re likely in read-only/browse-only mode. Ask the assistant what mode you’re in and what the fallback is.
Ask:
“Is this blocked by host capabilities, mode/policy, or the ‘allow upgrade’ requirement? What’s the recommended workaround?”