Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowTry your skills in the Power BI Dataviz World Championship! Round one ends June 26. Join now
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
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |