Showing posts with label explain. Show all posts
Showing posts with label explain. Show all posts

Friday, March 30, 2012

Parameter problem with OLAP and spaces

Hello all,

I have an issue with parameters. Let me explain.....

I have report1 which uses analysis services as it's data source. The report displays a list of our companies sites along with some costs etc. Site names can include spaces and numbers but they are stored in the relational database as varchar[50]. On the relevant text box of report1 I have defined a data detsination using report2 and passing it the site name field.value.

On report2 I have added the site name field as a filter dimension and set it as a parameter. On the report parameters I have set the parameter as being non queried.

When I run report1 and click a value to "drill down" it only works for values that have no spaces and no numbers. If If convert spaces to underscores I get a little further, but sites that have numbers, for example 15_OxfordStreet still do not work. The error message I get is..

"Parser: The syntax for '_Oxford' is incorrect.

Can anyone suggest anything to help?

Many thanks

Matt

You may need to escape the member names. To avoid similar issues, the SSAS team introduced undocumented function UrlEscapeFragment. If you open the sample AW cube, flip to the Actions tab in the Cube Designer, select the Sales Reason Comparision action, and expand the Parameters section, you will see how this function is used to escape the member name.|||

Teo,

Thanks for your reply. I'm still learning SQL 2005 and although I tried your suggestion I could not get it to work. However I did fix the problem. The issue was that I was passing through the "friendly name" of the value, instead of [data1].[field name].&[0] etc. as the jump to parameter!

Arrrrgggg...so simple when you think about it!

M

Monday, March 26, 2012

Parameter default not updating on deploy

I've got an issue with a report of mine where the default parameter isn't being cleared. Let me explain...

I created a report with a parameter on it. While I'm working on the cosmetics of the report, I didn't want to have to keep typing in a value just to see it run, so I set the default value on the parameter. I finish the report and deploy it and everything is ok. Then when I go to the page to view it, I notice that the default is still there, so I go back and edit my report to take out the default and just use NULL. In the preview tab, it looks ok, so I deploy the report again. Now when I go to the report, it still has the default value in the parameter box.

Does anyone have any idea as to why this is happening? The only way I could get around it is to drop the parameter from the report, deploy it, then re-add the parameter and deploy it again.

Thanks in advance,

Jarret

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=960767&SiteID=1