Comments on Reporting Tales - Inside news on Pentaho Reporting: Back to the start - MDX parametrization revisited

Interestingly, JPivot seems to strip curly braces ...

2010-07-22T03:18:15.131+01:00

Interestingly, JPivot seems to strip curly braces and some other "complete" member identification. I need to test a bit more, but find that if I submit {[Client Location].[Client Location.Clients].[All Clients].[COLORADO]} it will reformat the MDX to [Client Location.Clients].[COLORADO].

In PRD, I have found that once a query is parameterized and you cannot get to the variables anymore, PRD can lose connection to the field variables. You can copy and paste information from one report to another, and the second report will not work. I have had to pull the variables from the PRD query to get the fields to place on the report.

I really like 3.6. I have been using Pentaho off and on for 4 years and this version rocks. I am already hearing 3.7 and 4.0 upgrades that will be even mo' better yet.

Yes, the ${..} is a mindless string replacement. ...

2010-07-22T00:24:02.045+01:00

Yes, the ${..} is a mindless string replacement.

According to the examples on the MSDN documentation for MDX, you always have to use the curly braces (ie the set syntax).

http://msdn.microsoft.com/en-us/library/ms146052.aspx

Therefore, if myVariable is "[Client].[Location].[All Locations]" you probably get a syntax error.

Ok, so then is it possible to simply place a ${var...

2010-07-21T17:42:47.301+01:00

Ok, so then is it possible to simply place a ${variable} in a MDX query to have dynamic rows or columns? Thus,
select ${myVariable} on COLUMNS,
{[Measures].[MyMeasure1], [Measures].[MyMeasure2]} on ROWS
from [Monthly Data]

Where myVariable can be [Client].[Location].[All Locations] or {[Client].[Location].[WASHINGTON], [Client].[Location].[COLORADO]}

I have been trying to get this in PRD and have not been able to do so.

Ok, so then is it possible to simply place a ${var...

2010-07-21T17:41:40.323+01:00