SubsetCreatebyMDX(vSubName,'{EXCEPT({ TM1SUBSETALL( ['|vDimName|'] )},{ [Tata], [Ticky]) })} ;
While i am excuting my TI process with above line of code i am getting the below error can someone help me as its urgent
error:
Error: Prolog procedure line (22): Could not create dynamic subset:
Level or member name "Tata" ambiguous: found in dimensions "Test_Test", "Product_name" expression:
{EXCEPT({ TM1SUBSETALL( [product_name] )},{ [Ticky],[Tata] })}
Mdx issue
-
- Regular Participant
- Posts: 155
- Joined: Fri May 20, 2011 8:17 am
- OLAP Product: Applix,Cognos TM!
- Version: applix9.0Cognos tm1 9.5.1
- Excel Version: Excel 2010 2007
-
- Community Contributor
- Posts: 248
- Joined: Tue Nov 01, 2011 10:31 am
- OLAP Product: TM1
- Version: All
- Excel Version: All
- Location: Manchester
- Contact:
Re: Mdx issue
It means the element Tata is available in multiple dimensions
http://www-01.ibm.com/support/docview.w ... wg21454707
http://www-01.ibm.com/support/docview.w ... wg21454707
-
- Regular Participant
- Posts: 155
- Joined: Fri May 20, 2011 8:17 am
- OLAP Product: Applix,Cognos TM!
- Version: applix9.0Cognos tm1 9.5.1
- Excel Version: Excel 2010 2007
Re: Mdx issue
Thanks Edwart,
How to incorporate can you please help by altering the line that i shared
How to incorporate can you please help by altering the line that i shared
-
- MVP
- Posts: 2831
- Joined: Tue Feb 16, 2010 2:39 pm
- OLAP Product: TM1, Palo
- Version: Beginning of time thru 10.2
- Excel Version: 2003-2007-2010-2013
- Location: Atlanta, GA
- Contact:
Re: Mdx issue
To specify a member name in MDX you should use the [DimName].[MemberName] syntax. Specifying just the member name works as long as you don't have any duplicate member names but it can come back to bite you. I really wish the MDX recorder didn't do this.
- gtonkin
- MVP
- Posts: 1198
- Joined: Thu May 06, 2010 3:03 pm
- OLAP Product: TM1
- Version: Latest and greatest
- Excel Version: Office 365 64-bit
- Location: JHB, South Africa
- Contact:
Re: Mdx issue
As a quick tip, from the subset editor, right click the element you want and select Copy Unique Name
This will copy the Element with the Dimension name in the correct format to avoid ambiguity e.g. [Product_Name].[Tata]
Best to do this after you have recorded an expression or whenever writing MDX, often quicker and safer than typing out long dimension names.
This will copy the Element with the Dimension name in the correct format to avoid ambiguity e.g. [Product_Name].[Tata]
Best to do this after you have recorded an expression or whenever writing MDX, often quicker and safer than typing out long dimension names.
-
- Community Contributor
- Posts: 248
- Joined: Tue Nov 01, 2011 10:31 am
- OLAP Product: TM1
- Version: All
- Excel Version: All
- Location: Manchester
- Contact:
Re: Mdx issue
The original message indicated the ambiguity was between Product.Name and Test_Test.
Depending on the requirements and usage of the dimension Test_Test you could remove this dimension to absolve the ambiguity
Depending on the requirements and usage of the dimension Test_Test you could remove this dimension to absolve the ambiguity