Forum Discussion
Metadata Translation Not Applied to Renamed Column/Measure Names in Visuals
- 8 months ago
Hi ニック
This behavior is expected and works by design in Power BI.
Metadata translations (via Translation Builder / Tabular Editor) apply only to model-level metadata — meaning column names and measure names as they exist in the model.
When you rename a column or measure inside a visual, Power BI treats that text as a hard-coded label and completely bypasses metadata translations. As a result, translations will never be applied to those renamed fields in the Service or Desktop.Because of this:
Yes, you should avoid renaming columns or measures at the visual level if you plan to use translations.
Visual-level renaming should be considered incompatible with multi-language reports.
Regarding reverting renamed fields:
There is no automatic “reset to original name” option.
To revert, you must remove the field from the visual and add it again from the Fields pane, which restores the model name.
Best practice solution:
Perform all renaming at the model level only (tables, columns, and measures).
Define translations on those model objects.
Remove any visually renamed fields and re-add them after the model names and translations are finalized.
If your report was built with extensive visual-level renaming, this isn’t a translation issue — it’s technical debt. Cleaning it up is required for translations to work correctl
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
Hi ニック
This behavior is expected and works by design in Power BI.
Metadata translations (via Translation Builder / Tabular Editor) apply only to model-level metadata — meaning column names and measure names as they exist in the model.
When you rename a column or measure inside a visual, Power BI treats that text as a hard-coded label and completely bypasses metadata translations. As a result, translations will never be applied to those renamed fields in the Service or Desktop.
Because of this:
Yes, you should avoid renaming columns or measures at the visual level if you plan to use translations.
Visual-level renaming should be considered incompatible with multi-language reports.
Regarding reverting renamed fields:
There is no automatic “reset to original name” option.
To revert, you must remove the field from the visual and add it again from the Fields pane, which restores the model name.
Best practice solution:
Perform all renaming at the model level only (tables, columns, and measures).
Define translations on those model objects.
Remove any visually renamed fields and re-add them after the model names and translations are finalized.
If your report was built with extensive visual-level renaming, this isn’t a translation issue — it’s technical debt. Cleaning it up is required for translations to work correctl
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly