Applied Microsoft Analysis Services 2005

Re: UniqueKey "&" Special Character and Reporting Services

Teo Lachev — Mon, 11 Sep 2006 01:38:57 GMT

Thank you for solving this dilemma. %2526 did the trick. I attached a test harness that demonstrates how the sample Daily Product Sales.rdl (used in Chapter 18) can be called.

Re: UniqueKey "&" Special Character and Reporting Services

geoff — Fri, 08 Sep 2006 18:06:42 GMT

Yes the %26 does work for Url addresses in the Jump to URL. %26 goes to & after the parameters are parsed. You need %2526 if you put a javascript routine in the Jump to URL because it gets processed by the browser twice. %2526 goes to %26 goes to &

Re: UniqueKey "&" Special Character and Reporting Services

Teo Lachev — Thu, 07 Sep 2006 21:06:28 GMT

Have you tried the %26 encoding and did it work? At the time of writing the book I tried all sorts of hacks including %26 to no avail. I mentioned this to the SSRS and SSAS teams but no workaround was provided. I've noticed that the SSAS team has implemented the undocumented URLEscapeFragment() function to get around the same issue. The problem with SSRS though is that the browser "helpfully" unescapes the escaped & on the way out. Please let me know if you get it to work.

UniqueKey "&" Special Character and Reporting Services

geoff — Thu, 07 Sep 2006 20:27:42 GMT

Ch 18 states a problem with using "Jump to Url" to link to other reports with the generated parameter value as the UniqueKey in OLAP datasets.

UniqueKey uses an "&" to denote the member Key and this gets interpreted on the parameter string of the URL as the end of one parameter and the beginning of another.

The solution I'm suggesting is to escape the "&" as %26 for direct addresses and double escape the "&" as %2526 for javascript addresses.

By the way Reporting Services seems very useful for Analysis Services.

Geoff