Friday, March 23, 2012

Excel 2007, MDX Compatibility and connection string (for ragged dimensions)

I'm trying to open a simple SSAS 2005 cube with a ragged hierarchy (it has a level that contains member that should be hidden if the member name is the same as the parent).

I read about the necessity to use MDX Compatibility=2 into the connection string to see the HideMemberIf property in action. The dimension browser in BIDS does not display a member into a level only if it has no visible childs. May be this is a browser issue, as I read somewhere...

With Excel 2007, it should be possible to change the connection string. Unfortunately, even if I change it, Excel 2007 force the "MDX Compatibility=1" into my connection string. Moreover, it adds a "Safety Options=2" and "MDX Missing Member Mode=Error" and even if I try to change them, Excel still recreate the same connection string.

Is there someone that:

- has been successful using ragged hierarchies with Analysis Services 2005?

- has been able to change the connection string into Excel 2007?

Thank you

Marco Russo
http://www.sqlbi.eu
http://www.sqljunkies.com/weblog/sqlbi

Not tried them with Excel 2007, I'm afraid - it's always seemed pretty dumb to me that the default was that ragged hierarchies weren't displayed properly anyway. And what's worse is that in AS2005 you can't force the MDX compatibility property on the server either:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=653115&SiteID=1

Can we get this fixed please?

Chris

|||

Hi Chris,

I just posted in Excel 2007 forum another annoying issue.

By default, Excel 2007 display calculated measures but not calculated members on other dimensions.
You have to change this pivottable option settings each time. For each Pivot Table you create.

I asked it there is a way (eventually with a registry hack) to change this default...

Marco Russo
http://www.sqlbi.eu
http://www.sqljunkies.com/weblog/sqlbi

|||

Hi there,

Has anyone seen any updated information on the ragged hierarchy issue? I am having problems with setting MDX Compatibility = 2. Excel resets it back to 1.

Cheers

No comments:

Post a Comment