Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
XML
data.xmlanalysis
mappoint.webservice
msf
msxml-webrelease
netmyservices.sdk
passport.sdk
soap
soapsdk
uddi.general
uddi.programming
uddi.specification
xml
xmlsqlwebrelease
xsl
  
 
date: Thu, 28 Jul 2005 09:37:27 +1000,    group: microsoft.public.data.xmlanalysis        back       


Calculated member error   
Hello all,

I am experiencing an error with XMLA involving a calculated member.

The following MDX query runs with no problem:
WITH
SET MeasuresSet AS '{[Measures].[Unit Sales],[Measures].[Store 
Cost],[Measures].[Store Sales]}'
SET StoreSet AS 'HIERARCHIZE(DISTINCT(ADDCALCULATEDMEMBERS({[Store].[All 
Stores].[USA].[CA]})))'
MEMBER [Product].[All Products].[Drinks] AS '[Product].[All 
Products].[Drink]'
SELECT
NON EMPTY {MeasuresSet} PROPERTIES CHILDREN_CARDINALITY, 
DIMENSION_UNIQUE_NAME, HIERARCHY_UNIQUE_NAME, DESCRIPTION, MEMBER_ORDINAL, 
MEMBER_TYPE, PARENT_COUNT, PARENT_LEVEL, PARENT_UNIQUE_NAME ON 0,
NON EMPTY {CROSSJOIN({[Product].[All Products].[Drinks]},StoreSet)} 
PROPERTIES CHILDREN_CARDINALITY, DIMENSION_UNIQUE_NAME, 
HIERARCHY_UNIQUE_NAME, DESCRIPTION, MEMBER_ORDINAL, MEMBER_TYPE, 
PARENT_COUNT, PARENT_LEVEL, PARENT_UNIQUE_NAME ON 1 FROM Sales CELL 
PROPERTIES FONT_FLAGS, FORMATTED_VALUE, VALUE, BACK_COLOR, FORE_COLOR

However, this MDX fails:
WITH
SET MeasuresSet AS '{[Measures].[Unit Sales],[Measures].[Store 
Cost],[Measures].[Store Sales]}'
SET StoreSet AS 'HIERARCHIZE(DISTINCT(ADDCALCULATEDMEMBERS({[Store].[All 
Stores].[USA].[CA]})))'
MEMBER [Product].[All Products].[Drinks] AS '[Product].[All 
Products].[Drink]'
SELECT
NON EMPTY {MeasuresSet} PROPERTIES CHILDREN_CARDINALITY, 
DIMENSION_UNIQUE_NAME, HIERARCHY_UNIQUE_NAME, DESCRIPTION, MEMBER_ORDINAL, 
MEMBER_TYPE, PARENT_COUNT, PARENT_LEVEL, PARENT_UNIQUE_NAME ON 0,
NON EMPTY {CROSSJOIN(StoreSet,{[Product].[All Products].[Drinks]})} 
PROPERTIES CHILDREN_CARDINALITY, DIMENSION_UNIQUE_NAME, 
HIERARCHY_UNIQUE_NAME, DESCRIPTION, MEMBER_ORDINAL, MEMBER_TYPE, 
PARENT_COUNT, PARENT_LEVEL, PARENT_UNIQUE_NAME ON 1 FROM Sales CELL 
PROPERTIES FONT_FLAGS, FORMATTED_VALUE, VALUE, BACK_COLOR, FORE_COLOR

The only difference is the order that the calculated member '[Product].[All 
Products].[Drinks]' appears in the Axis 1 set.

Both queries run without a problem in the Analysis Services MDX sample 
application.

Any ideas?

Thanks, Patrick Williamson
date: Thu, 28 Jul 2005 09:37:27 +1000   author:   x

Re: Calculated member error   
Hi Patrick, what is the error you see?

Thanks,
Akshai
--
This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"x"  wrote in message
news:e9KmnQwkFHA.3336@tk2msftngp13.phx.gbl...
> Hello all,
>
> I am experiencing an error with XMLA involving a calculated member.
>
> The following MDX query runs with no problem:
> WITH
> SET MeasuresSet AS '{[Measures].[Unit Sales],[Measures].[Store
> Cost],[Measures].[Store Sales]}'
> SET StoreSet AS 'HIERARCHIZE(DISTINCT(ADDCALCULATEDMEMBERS({[Store].[All
> Stores].[USA].[CA]})))'
> MEMBER [Product].[All Products].[Drinks] AS '[Product].[All
> Products].[Drink]'
> SELECT
> NON EMPTY {MeasuresSet} PROPERTIES CHILDREN_CARDINALITY,
> DIMENSION_UNIQUE_NAME, HIERARCHY_UNIQUE_NAME, DESCRIPTION, MEMBER_ORDINAL,
> MEMBER_TYPE, PARENT_COUNT, PARENT_LEVEL, PARENT_UNIQUE_NAME ON 0,
> NON EMPTY {CROSSJOIN({[Product].[All Products].[Drinks]},StoreSet)}
> PROPERTIES CHILDREN_CARDINALITY, DIMENSION_UNIQUE_NAME,
> HIERARCHY_UNIQUE_NAME, DESCRIPTION, MEMBER_ORDINAL, MEMBER_TYPE,
> PARENT_COUNT, PARENT_LEVEL, PARENT_UNIQUE_NAME ON 1 FROM Sales CELL
> PROPERTIES FONT_FLAGS, FORMATTED_VALUE, VALUE, BACK_COLOR, FORE_COLOR
>
> However, this MDX fails:
> WITH
> SET MeasuresSet AS '{[Measures].[Unit Sales],[Measures].[Store
> Cost],[Measures].[Store Sales]}'
> SET StoreSet AS 'HIERARCHIZE(DISTINCT(ADDCALCULATEDMEMBERS({[Store].[All
> Stores].[USA].[CA]})))'
> MEMBER [Product].[All Products].[Drinks] AS '[Product].[All
> Products].[Drink]'
> SELECT
> NON EMPTY {MeasuresSet} PROPERTIES CHILDREN_CARDINALITY,
> DIMENSION_UNIQUE_NAME, HIERARCHY_UNIQUE_NAME, DESCRIPTION, MEMBER_ORDINAL,
> MEMBER_TYPE, PARENT_COUNT, PARENT_LEVEL, PARENT_UNIQUE_NAME ON 0,
> NON EMPTY {CROSSJOIN(StoreSet,{[Product].[All Products].[Drinks]})}
> PROPERTIES CHILDREN_CARDINALITY, DIMENSION_UNIQUE_NAME,
> HIERARCHY_UNIQUE_NAME, DESCRIPTION, MEMBER_ORDINAL, MEMBER_TYPE,
> PARENT_COUNT, PARENT_LEVEL, PARENT_UNIQUE_NAME ON 1 FROM Sales CELL
> PROPERTIES FONT_FLAGS, FORMATTED_VALUE, VALUE, BACK_COLOR, FORE_COLOR
>
> The only difference is the order that the calculated member
'[Product].[All
> Products].[Drinks]' appears in the Axis 1 set.
>
> Both queries run without a problem in the Analysis Services MDX sample
> application.
>
> Any ideas?
>
> Thanks, Patrick Williamson
>
>
date: Tue, 2 Aug 2005 12:40:18 -0700   author:   Akshai Mirchandani [MS]

Re: Calculated member error   
Hi Akshai,

The error I am getting is:
Formula error - cannot find dimension member ("[Product].[All 
Products].[Drinks]") - in  a name-binding function'

Thanks, Patrick


"Akshai Mirchandani [MS]"  wrote in message 
news:uOzLEo5lFHA.936@TK2MSFTNGP09.phx.gbl...
> Hi Patrick, what is the error you see?
>
> Thanks,
> Akshai
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
> Please do not send email directly to this alias. This alias is for 
> newsgroup
> purposes only.
>
> "x"  wrote in message
> news:e9KmnQwkFHA.3336@tk2msftngp13.phx.gbl...
>> Hello all,
>>
>> I am experiencing an error with XMLA involving a calculated member.
>>
>> The following MDX query runs with no problem:
>> WITH
>> SET MeasuresSet AS '{[Measures].[Unit Sales],[Measures].[Store
>> Cost],[Measures].[Store Sales]}'
>> SET StoreSet AS 'HIERARCHIZE(DISTINCT(ADDCALCULATEDMEMBERS({[Store].[All
>> Stores].[USA].[CA]})))'
>> MEMBER [Product].[All Products].[Drinks] AS '[Product].[All
>> Products].[Drink]'
>> SELECT
>> NON EMPTY {MeasuresSet} PROPERTIES CHILDREN_CARDINALITY,
>> DIMENSION_UNIQUE_NAME, HIERARCHY_UNIQUE_NAME, DESCRIPTION, 
>> MEMBER_ORDINAL,
>> MEMBER_TYPE, PARENT_COUNT, PARENT_LEVEL, PARENT_UNIQUE_NAME ON 0,
>> NON EMPTY {CROSSJOIN({[Product].[All Products].[Drinks]},StoreSet)}
>> PROPERTIES CHILDREN_CARDINALITY, DIMENSION_UNIQUE_NAME,
>> HIERARCHY_UNIQUE_NAME, DESCRIPTION, MEMBER_ORDINAL, MEMBER_TYPE,
>> PARENT_COUNT, PARENT_LEVEL, PARENT_UNIQUE_NAME ON 1 FROM Sales CELL
>> PROPERTIES FONT_FLAGS, FORMATTED_VALUE, VALUE, BACK_COLOR, FORE_COLOR
>>
>> However, this MDX fails:
>> WITH
>> SET MeasuresSet AS '{[Measures].[Unit Sales],[Measures].[Store
>> Cost],[Measures].[Store Sales]}'
>> SET StoreSet AS 'HIERARCHIZE(DISTINCT(ADDCALCULATEDMEMBERS({[Store].[All
>> Stores].[USA].[CA]})))'
>> MEMBER [Product].[All Products].[Drinks] AS '[Product].[All
>> Products].[Drink]'
>> SELECT
>> NON EMPTY {MeasuresSet} PROPERTIES CHILDREN_CARDINALITY,
>> DIMENSION_UNIQUE_NAME, HIERARCHY_UNIQUE_NAME, DESCRIPTION, 
>> MEMBER_ORDINAL,
>> MEMBER_TYPE, PARENT_COUNT, PARENT_LEVEL, PARENT_UNIQUE_NAME ON 0,
>> NON EMPTY {CROSSJOIN(StoreSet,{[Product].[All Products].[Drinks]})}
>> PROPERTIES CHILDREN_CARDINALITY, DIMENSION_UNIQUE_NAME,
>> HIERARCHY_UNIQUE_NAME, DESCRIPTION, MEMBER_ORDINAL, MEMBER_TYPE,
>> PARENT_COUNT, PARENT_LEVEL, PARENT_UNIQUE_NAME ON 1 FROM Sales CELL
>> PROPERTIES FONT_FLAGS, FORMATTED_VALUE, VALUE, BACK_COLOR, FORE_COLOR
>>
>> The only difference is the order that the calculated member
> '[Product].[All
>> Products].[Drinks]' appears in the Axis 1 set.
>>
>> Both queries run without a problem in the Analysis Services MDX sample
>> application.
>>
>> Any ideas?
>>
>> Thanks, Patrick Williamson
>>
>>
>
>
date: Thu, 4 Aug 2005 10:19:48 +1000   author:   x

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us