Forum Discussion
January 2022 PBI RS: Parameter values from query string are not properly decoded in RDL report
- 4 years ago
SagarSalvi wrote:
We are expecting fix from reporting module.
Then you really need to log an official support ticket.
I did a quick test with HttpUtility.UrlEncode and UrlDecode and I can confirm that the encode does use + to encode spaces and the decode works correctly with this so to me it does look like a bug of some sort. But only Microsoft support could confirm if this is a bug or a specific design decision.
I can tell you that 2 possible work arounds are to either use %20 for space encoding or to use the /reportserver endpoint instead of the /reports one, but if you want Microsoft to consider a code fix on their side a support ticket is the best approach.
- 4 years ago
Wanted to reply that this has been fixed and will be released in the May release of Power BI Report Server.
- 3 years ago
Thought to update this post. This issue is fixed by MSFT in PBI RS September 2022.
D_W thank you for taking a look at the issue. Actually its one of our module which generates the URL dynamically and it uses HTTPUtility.URLEncode(). This module is not touched since long time bcoz everythings working fine uptil now. We are doing monthly releases and now we have 100s of different versions. All our customers are on different version. Its wont make sense to backport this code fix to all old versions. We are expecting fix from reporting module.
SagarSalvi wrote:
We are expecting fix from reporting module.
Then you really need to log an official support ticket.
I did a quick test with HttpUtility.UrlEncode and UrlDecode and I can confirm that the encode does use + to encode spaces and the decode works correctly with this so to me it does look like a bug of some sort. But only Microsoft support could confirm if this is a bug or a specific design decision.
I can tell you that 2 possible work arounds are to either use %20 for space encoding or to use the /reportserver endpoint instead of the /reports one, but if you want Microsoft to consider a code fix on their side a support ticket is the best approach.
- SagarSalvi4 years ago
Helper I
Yes we have a ticket with MSFT for this issue. We already met them once and demoed them the issue. They want their manager to review it. I will let you know once I have any concrete answer from them.