Hello, All!
I'm using ParallelPeriod function to compare actual values with previous
year values. It works fine, until I hide some members in my heirarchy (using
'Hide member if' property). After that, Analysis Manager Cube Browser
reports the following error:
"Formula Error - the function does not support ragged hierarchies"
Clients like ProClarity or Crystal Analysis show empty cells for the same
reason
The most interesting is that Excel PivotTable shows valid numbers without
any error reports!
So here are my questions:
1. Is there any workaround to this error? I need hidden members for the
goals of plan-to-fact analysis and I also need ParallelPeriod for previous
year comparison. Is there an MDX code to replace ParallelPeriod call and to
avoid this error? Are there any additional properties I can specify to tell
MS AS that my hierarchy is not ragged?
2. What is the difference in Excel's interaction with the OLAP service? It
apparently treats MDX calculations in some other way than other clients do!


With best regards, Andrew Surinov. E-mail: sav (AT) tut (DOT) by

Hello, Matt!

Yes, that was the problem, thanks!
When I set MDX Compatibility=2 , error is displayed, with MDX
Compatibility=1 correct values are displayed
But MDX Sample Application also works well with an empty connection string,
does that mean that the other clients explicitly specify MDX
Compatibility=2 in thier connection strings? Now I'm trying to figure out
how to override connection string in ProClarity and Crystal Analysis
What is the client-side registry entry for this property?

You wrote on Wed, 6 Aug 2003 10:36:51 -0700:

MCM> I'm a connection string property is causing the different behavior in
MCM> Excel. I'd start by looking at
MCM> MDX Compatibility Property. See PivotTable Service Properties in
MCM> under PivotTable Service Programmer's Reference in Books Online for a
MCM> complete listing of the connection string properties. You can
MCM> experiment with the properties in the MDX Sample by appending any
MCM> desired properties after the server name. e.g. MyServerName;MDX
MCM> Compatibility=1

MCM> - Matt Carroll

With best regards, Andrew Surinov. E-mail: sav (AT) tut (DOT) by

From books online topic for MDX Compatibility Property:
This property overrides the following registry setting:

HKEY_CLASSES_ROOT\CLSID\{a07ccd0c-8148-11d0-87bb-00c04fc33942}
- Matt Carroll
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Andrew Surinov" <sav (AT) tut (DOT) by> wrote