Posted 20 November 2019, 12:56 am EST
We are are attempting to upgrade v12 to v13. In testing with the latest hotfix v13.2.18593.0 we have found that “jump to url” hyperlinks are double encoded when rendered to html which causes hyperlinks with ampersands (query string parameters) to be broken.
The href out will encode ampersands as & when it should be just &
This is a blocking issue as we have many reports that link to web pages using query string parameters that no longer work.
Looking through your code with a decompiler I can see that you are calling XhtmlTextWriter.HtmlEncode on the url then passing to a XmlTextWriter which also does encoding for the attribute leading to a double encode.
Attached is a sample report with an example export output, it makes a link to Google which should have both the search string and the site limiter but the site limiter does not work because the second query parameter can’t be parsed properly.
The links work fine in the pdf export and in v12 html export.