Comments on: Re: MDX ORDER Riddle

By: Sam Kane

Sam Kane — Wed, 16 Mar 2011 20:10:52 +0000

Here are this and some other articles on Sorting dimensional members:

http://ssas-wiki.com/w/Articles#Sorting_dimensional_members

By: Tomislav Piasevoli

Tomislav Piasevoli — Tue, 18 May 2010 09:00:00 +0000

Maybe I wasn’t clear enough @Elizabeth. You might end up either with false results (not in this example but in some other calculations) or with the Order() function not working as you expected for example. So, either something will not work as you expect (that’s benign because it’s easy to spot) or you’ll get wrong results (which you may not notice right away). I’m talking about rare cases, this is not a common issue. The problem arises (only?) when you have layers of calculation with related hierarchies and you’re not taking that into account in your calculations. Seeing them as flat is wrong.

By: Tomislav Piasevoli

Tomislav Piasevoli — Tue, 18 May 2010 08:00:00 +0000

@Elizabeth, that was the summary part. Explanation, quite a long one, is above that. In short, if you don't specify the current member inside the tuple (exactly as that: "something.CurrentMember"), related hierarchy's member will trigger attribute relations mechanism and all the "members" that are not there will be changed. Being explicitely there and not being there explicitely but implicitely is totally different thing, that's what I ment in the summary part. If you're not there, you might change. If you are, you won't change. Of course, it only matters when there are related hierarchies in tuple/coordinate, if not, it doesn't matter if you put current member in the tuple or not.

OK?

@Boyan, I will.

By: Elizabeth

Elizabeth — Mon, 17 May 2010 00:00:00 +0000

thanks Tomislav~but important thing to remember?how? thanks

By: Boyan

Boyan — Wed, 30 Nov -0001 00:00:00 +0000

Hi Tomislav, please have a look at:

http://www.bp-msbi.com/2010/05/re-re-mdx-order-riddle/

For a bit more on the subject.