Quantcast
Channel: Pentaho Community Forums
Viewing all articles
Browse latest Browse all 16689

Why does a calculated member not belong to the level I define it?

$
0
0
Pentaho BI Server 4.8 CE.

This MDX produces a result:


Code:

WITH MEMBER [Items].[ItemType].[NonSales] as
[Items].[ItemType].[Deposit] + [Items].[ItemType].[Gift_Voucher]
SELECT {[Items].[NonSales]} ON COLUMNS,
[Measures].[AmtPaidExclGST] on rows
FROM [sales]


(the Dimension is Items. It has one Hierarchy, unnamed, and one level called ItemType.)

However, this doesn't:

Code:

WITH MEMBER [Items].[ItemType].[NonSales] as
 [Items].[ItemType].[Deposit] + [Items].[ItemType].[Gift_Voucher]
SELECT {[Items].[ItemType].[NonSales]} ON COLUMNS,
[Measures].[AmtPaidExclGST] on rows
FROM [sales]

When I read MDX documentation it says that if I create a member fully qualified like this, it should end up in the level I expect.
But how come the second query doesn't work?

Probably I don't understand something.
Microsoft says that a calculated member like mine should end up as a member of the [ItemType] level, but their actual code example uses the partially qualified syntax that works in my case too.

http://msdn.microsoft.com/en-us/library/ms146017.aspx (see the BigSeller calculated member about 60% down the page).

Viewing all articles
Browse latest Browse all 16689

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>