Localization
manage_localization manages cultures and translations for model metadata (captions and descriptions).
Use it when you need the semantic model to feel native for multiple audiences (for example, English + French captions for measures and columns).
Important: localization changes metadata only. It does not translate DAX/M logic or change how measures calculate.
You don’t need to know tool parameters-tell the LLM which cultures you support and what should be translated first, and it will use manage_localization behind the scenes.
What to ask the LLM (quick prompts)
“Add culturefr-FR and translate captions for our top 20 finance measures. Show proposed translations before applying.”
“Set the German caption/description for measure [Gross Margin %].”
“List missing translations for de-DE and propose a prioritized fill plan.”
“Remove culture it-IT (we no longer support it).”
What you can localize (and what you can’t)
You can manage:
- Cultures (for example
en-US,fr-FR,de-DE) - Translated captions and descriptions for:
- tables
- columns
- measures
- hierarchies
You cannot:
- Translate DAX expressions, M queries, or partition logic
- Translate report visuals (this is semantic-model metadata only)
If you want “business term” mapping for the assistant (not UI localization), use:
Risk & governance notes (read this once)
Recommended workflow (how to do localization that sticks)
1) Start with a glossary (consistency wins)
Provide a short glossary for the assistant to follow:
“Use consistent translations: ‘Gross Margin’ → ‘Marge brute’, ‘Net Sales’ → ‘Ventes nettes’. Apply across measure captions infr-FR.”
2) Translate what users see most
Start with:
- top measures (KPIs)
- table captions
- commonly used columns in slicers
Prompt:
“Forfr-FR, translate captions for the top 20 measures used in finance reporting. Use short, business-friendly wording. Show the proposed translations before applying.”
3) Fill the gaps (coverage pass)
“List missing translations forde-DE (captions and descriptions) and propose a prioritized fill plan.”
4) Maintain over time (after renames/new objects)
“We added/renamed measures. Re-scan translations forfr-FR and list what’s missing or stale.”
Quality tips (what makes localization good)
- Keep captions short; descriptions can be longer.
- Prefer business terminology over literal/technical translations.
- Avoid translating code-like tokens (table/column names) inside parentheses or brackets unless your org standard says otherwise.
- If your org has a style guide, paste it once and ask the assistant to follow it consistently.
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); metadata-only (captions/descriptions), not DAX/M translation.
If localization edits are blocked, ask:
“Give me a translation plan and a checklist I can apply manually in Desktop.”Troubleshooting
Ask the assistant to reload metadata and re-check the cultures list. If you’re testing in Desktop, confirm you’re viewing the right culture in the UI.
Ask the assistant to list the target object (table + name) before applying the translation, and to show a preview of changes.
Ask:
“Generate a translation checklist by culture with missing captions/descriptions per object type.”