Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by watching the DP-600 session on-demand now through April 28th.
Learn moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. 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
Check out the April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
| User | Count |
|---|---|
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
| User | Count |
|---|---|
| 8 | |
| 8 | |
| 4 | |
| 3 | |
| 2 |