Forum Discussion
Advocate IPaginated URLs encoded differently depending on display language
Hi FilipAi
Apologies for the inconvenience caused. I recommend raising a support ticket so that our internal team can thoroughly investigate and assist you in resolving this issue as quickly as possible. We appreciate your patience and are here to help.
Note: https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
Thanks and regards,
Cheri SrikanthNo updates since 18 Feb (as ni the snippet) this year. I doubt that I will be informed personally by Microsoft if the issues is solved. Therefore I suggest this topic is closed/archived.
Community SupportHi FilipAi
Power BI behaves differently when switching to another language due to regional settings and encoding rules that vary based on the selected display language.
- Power BI automatically encodes URLs to handle different language-specific characters.
- Some languages (like Swedish) interpret spaces as +( %2B in URL encoding) instead of %20 (which is the standard space encoding in English).
- This behavior can cause issues when parameters in URLs are read incorrectly by the Power BI service.
Test in Different Browsers and Clear Cache:
- Sometimes, browsers handle encoding differently.
- Try running your Power BI report in Edge, Chrome, or Firefox.
If the above information helps you, please give us a Kudos and marked the reply Accept as a Solution.
Thanks,
Cheri Srikanth
FilipAiHelper I
I think it is an oversimplificatiopn to say that "Some languages (like Swedish) interpret spaces as +( %2B in URL encoding) instead of %20 (which is the standard space encoding in English)".
I noticed space is converted to a plus sign when opening the URL from a PBI report (both in Chrome and Edge). What happens next depends on display language in PBI and browser. If display language is set Swedish, the plus (converted space) is converted to %20 in Chrome, but to %2B in Edge. If set to English, both browsers convert it to %20.
I am not sure this is a browser issues, I see it rather as a PBI service inconsistency. Thus I am a but reluctant to mark it as solved.