MDX Validation error in Cognos 10.2 Report studio

[saisrujan]

Hi,

I am getting below error

XQE-EXE-0025 error

"The describeDataSourceQuery request is invalid. The request must contain a valid decribeDataSourceQuery element "

1. I have a SSAS cube(Go Sales Fact) in SQL server 2008 R2.
2. Created a Datasource(Go Sales Fact) in Cognos administration and Test Success for compatible and dynamic.
3. When I am trying to validate a MDX it is giving me above error. I have selected the Datasource(GO Sales Fact) and entered catalog as GO Sales Fact for MDX properties.

MDX

SELECT [Measures].[Gross Margin] ON COLUMNS,

[Order method].[Order Method Code] ON ROWS

FROM [GO Sales Fact]

NOTE: above query executes in SSAS.

find the screen shots as attachment.

[MFGF]

Hi,

I am getting below error

XQE-EXE-0025 error

"The describeDataSourceQuery request is invalid. The request must contain a valid decribeDataSourceQuery element "

1. I have a SSAS cube(Go Sales Fact) in SQL server 2008 R2.
2. Created a Datasource(Go Sales Fact) in Cognos administration and Test Success for compatible and dynamic.
3. When I am trying to validate a MDX it is giving me above error. I have selected the Datasource(GO Sales Fact) and entered catalog as GO Sales Fact for MDX properties.

MDX

SELECT [Measures].[Gross Margin] ON COLUMNS,

[Order method].[Order Method Code] ON ROWS

FROM [GO Sales Fact]

NOTE: above query executes in SSAS.

find the screen shots as attachment.

Are you saying you have created a report with manually-coded MDX in the query? If so, why? The whole idea is that the Cognos query engine codes the appropriate query for you as a result of dragging in the desired members/levels/measures into your report. Can you explain what you are trying to achieve?

MF.

[saisrujan]

Hello MF,

Yes...i am trying to validate manual MDX.

[MFGF]

Hello MF,

Yes...i am trying to validate manual MDX.

Why? What are you trying to achieve?

MF.

[TheFaster]

I'm going to jump on this post. Having the same issues. I understand the purpose for the users is to drag n' drop to make queries. However, I'm trying to make a tool that auto-generates MDX queries for certain purposes. In which case, user-defined MDX is necessary.

I'm getting the same errors when I try to run an MDX query though. And since I'm literally grabbing the Native MDX and trying to run it as a user-defined query, I shouldn't be running into any syntax issues.

Any ideas?

[CognosPaul]

Cognos does not support MDX using the dynamic query engine. Make sure you have a connection defined using the CQM if you want handwritten MDX.

It's been a long time since I've attempted to use handwritten, but I seem to remember that all of the sets and members need to have defined names Reference those in the various axes.

[TheFaster]

So you're saying DQM won't work?

[CognosPaul]

Correct. DQM works by intelligently modifying queries at run time. It is entirely incompatible with handwritten queries.

[TheFaster]

Alright, so based on that, would there be any way to figure out - programmatically - how many cells are being returned by a given MDX query being run in DQM?

[datapanda]

 :D

So, did anybody figure out how to overwrite the user-defined MDX in Cognos?
We're in Cognos 10.2, hitting an Microsoft SSAS Cube.
For some reason when hitting this SSAS cube Cognos creates horrible MDX, completely different than the cleaner one Analysis Services generates. For this reason, we have been tasked to try to overwrite the MDX behind the report studio report without breaking the shell of the report already running in PROD (just performing poorly).
I started creating some MDX for the prompts and everything was going great , until I faced the fact I wanted to do CROSSJOIN or (*) like we normally write it in Analysis Services. I have tried numerous ways to rewrite the syntax but cognos errors, it says it doesn't recognize that syntax. I actually tried even passing the same MDX cognos generates when dragging the data items directly from the cube but still the crossjoin "word" is a problem. Has anybody written complex MDX queries in the user-defined MDX Cognos? Do we know about any downside?

I appreciate your help in advance