Forum Discussion
Multilanguage Report - Publish public
- 1 year ago
Hi Anonymous,
You're very welcome!Great question! metadata translations (such as table and column names) from Translation Builder are stored in the model and automatically apply based on the user's locale in Power BI Service. However, since Publish to Web does not support locale detection, these translations will not work in public reports. Additionally, Translation Builder does not store translations in an accessible table, so they cannot be directly used in a slicer or bookmark.
The best alternative is to manually create a translation table within your dataset.
- If possible, copy the translations from Tabular Editor or the Translation Builder tool into a new table. Structure this table with translations for column headers, field names, and other metadata.
- Add a slicer to let users choose their preferred language. Use DAX measures to dynamically switch text labels based on the selected language.
- If applicable, create bookmarks for different language views so users can switch between them easily.
Since Publish to Web does not support automatic locale-based translations, this manual approach is the most effective way to handle multilingual reports.
If this helps, then please Accept it as a solution and dropping a "Kudos" so other members can find it more easily.
Hope this works for you!
Thanks.
Thanks again for your help.
How can i access the translations made with the "Translation Builder"? Is there a way to access it and safe it into a slicer or bookmark? For the datatranslations its clear, because it works with a slicer. Meta data will be always in the users locale i figured out, but what about the translations in the Translation builder Table?
Thanks
Hi Anonymous,
You're very welcome!
Great question! metadata translations (such as table and column names) from Translation Builder are stored in the model and automatically apply based on the user's locale in Power BI Service. However, since Publish to Web does not support locale detection, these translations will not work in public reports. Additionally, Translation Builder does not store translations in an accessible table, so they cannot be directly used in a slicer or bookmark.
The best alternative is to manually create a translation table within your dataset.
- If possible, copy the translations from Tabular Editor or the Translation Builder tool into a new table. Structure this table with translations for column headers, field names, and other metadata.
- Add a slicer to let users choose their preferred language. Use DAX measures to dynamically switch text labels based on the selected language.
- If applicable, create bookmarks for different language views so users can switch between them easily.
Since Publish to Web does not support automatic locale-based translations, this manual approach is the most effective way to handle multilingual reports.
If this helps, then please Accept it as a solution and dropping a "Kudos" so other members can find it more easily.
Hope this works for you!
Thanks.
- Anonymous1 year agoNot applicable
Thanks a lot! I will try that.