Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register 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
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 1 | |
| 1 |
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 2 |