I am using URL action to call to execute reports from reporting services. I
am passing dimension.currentmember.name. One member happens to have a # and
that seems to cause a problem as it does not get encoded in the URL.

When the same report is run by directly having the reporting services
connect to the cube, it converts the # into %23 and works fine.

How do I make my action URL work?

thanks

--
Message posted via http://www.sqlmonster.com

If Excel is installed on the Server, you can use Substitute() as following;

EXCEL!Substitute(Dimension.CurrentMember.Name, "#", "%23")

If not, you may need to create UDF to do the same thing.

Ohjoo Kwon

"Rama via SQLMonster.com" <forum (AT) SQLMonster (DOT) com> wrote

Thank you. I would need to identify all special characters and substitute
them. I was wondering if using currentmember.uniquename might solve the
problem, but am not sure I can define parameters in reporting services
reports to recognise uniquename instead of name.

Can you help with that?

thanks

--
Message posted via http://www.sqlmonster.com

Sorry - I also wanted to add
can you also let me know from where i can get help on creating UDF? Is
there something in MDX that I can use to resolve this? (like uniquename
instead of name)

thanks

--
Message posted via http://www.sqlmonster.com

Whether you use Name or UniqueName, the result string may still contain
special characters.

For UDF, see next titles from BOL.

- Creating and Using User-Defined Functions in MDX
- USE LIBRARY Statement

Ohjoo


"Rama via SQLMonster.com" <forum (AT) SQLMonster (DOT) com> wrote

Is there anyway you can use something besides the # character? That's the
HTML anchor character... maybe make the dimension name xx_number instead?
I'd shy away from ? and & too.
-m



"Rama via SQLMonster.com" <forum (AT) SQLMonster (DOT) com> wrote

No, i don't have control over special characters in data as OLTP systems
does not have any rules (and does not want to have any rules) to prevent
these special characters.

I will have to handle these in AS.

thank you

--
Message posted via http://www.sqlmonster.com