Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
According to https://github.com/Microsoft/PowerBI-visuals/blob/master/Visual/Locale.md, the properties panel gets localized in
./stringResources/<lang_key>.json
and the visual content can be localized since API 1.10 using the LocalizationManager, whose read its strings from
./stringResources/<lang_key>/resources.resjson
(<lang_key> is the ISO region code like "en_US").
While this seems to be true, I found out by accident, that the LocalizationManager also has no problem finding the strings in the first location.
I appreciate having just one file per language for all the strings and would like to know if it's okay to put everything in "./stringResources/<lang_key>.json" ?
Solved! Go to Solution.
We recommend to use resjson format only since Format Panel and localization manager work fine with this approach.
You can also check how we localize in-house visuals.
Ignat Vilesov,
Software Engineer
Microsoft Power BI Custom Visuals
We recommend to use resjson format only since Format Panel and localization manager work fine with this approach.
You can also check how we localize in-house visuals.
Ignat Vilesov,
Software Engineer
Microsoft Power BI Custom Visuals
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
6 | |
6 | |
3 | |
2 | |
2 |
User | Count |
---|---|
6 | |
5 | |
4 | |
4 | |
3 |