May 13, 2013 at 3:37 pm
Anyone know why the following doesnt work?
SELECT
{
[DimX].[DimId].Members,
[DimX].[DimId].currentmember.properties("value" )
} ON ROWS,
[Measures].[Mea_1] ON COLUMNS
FROM Measures
This keeps throwing the following exception:
Query (2, 2) The function expects a tuple set expression for the 2 argument. A string or numeric expression was used.
As an aside, is a way to maximize the performance of querying for member properties?
Thanks in advance
May 14, 2013 at 7:52 am
check this out :
MEMBER MyValue as 'DimX].[DimId].currentmember.properties("value")'
SELECT
{[DimX].[DimId].Members, MyValue} ON ROWS,
[Measures].[Mea_1] ON COLUMNS
FROM MyCube
also check out http://www.mdxsamples.com/ ...on why using properties is slow (see bottom para)
May 14, 2013 at 1:55 pm
robinrai3 (5/14/2013)
check this out :MEMBER MyValue as 'DimX].[DimId].currentmember.properties("value")'
SELECT
{[DimX].[DimId].Members, MyValue} ON ROWS,
[Measures].[Mea_1] ON COLUMNS
FROM MyCube
also check out http://www.mdxsamples.com/ ...on why using properties is slow (see bottom para)
Thanks for responding.
I see how you declare the member before the select. Is it possible to do this inline, after the select?
May 15, 2013 at 3:23 am
hi ,
I've been down the mineshaft on trying to learn mdx coming from a TSQL background ...its been one step foward, 3 back all the time...a real ball ache. Don't know why it does not work inline ...but works when declared as a member. One thing I've found is that doing all the donkey work in using declared sets and members seems to work in situations when you would think in line it would work as well
I'm no guru..but contact me again if you need further help...lets share the knowledge...
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply