I have a pretty simple ranking mechanism that ranks the number of
"Engagements" based on dynamic dimensions set up on Axis(1). I have a
calculated member in my cube called Engagement Rank with the following
MDX:
iif(IsError(Axis(1).Count) or IsEmpty([Measures].[Engagement Count]),
null,
Rank(Axis(1).Item(0).Item(Axis(1).Item
(0).Count-1).Hierarchy.CurrentMember,
Order(Extract(Axis(1), Axis(1).Item(0).Item(Axis(1).Item
(0).Count-1).Hierarchy), [Measures].[Engagement Count], BDESC)))
If I use the following MDX in SQL against my cube I get the following:
SELECT { [Measures].[Engagement Count], [Measures].[Engagement Rank] }
ON AXIS(0),
NON EMPTY [Organization].[Region].[Region].MEMBERS
ON AXIS(1)
FROM [EI Portal Cube]
My result is exactly what I want to see:
Region Engagement Count Engagement Rank
East
25 4
West
75 1
North
34 3
South
68 2
However, when I use the SQL "Browse Cube" method (and I presume in
Excel) and drag the Region dimension and measures onto the screen, I
get the following:
Region Engagement Count Engagement Rank
East
25 2
West
75 2
North
34 2
South
68 2
Has anyone seen this before? Are there subcubes or something else
involved that is throwing my Axis MDX off? Props to Mosha and Deepak -
the code above was cobbled togther from their very useful posts.
Thanks!
Sincerely,
J'son
Hi guys,
Still haven't heard a response.. has anyone heard of the situation
above?
Thanks again,
J'son