Page 1 of 1
Mdx issue
Posted: Tue Sep 22, 2015 3:20 pm
by mincharug.shulft
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] })}
Re: Mdx issue
Posted: Tue Sep 22, 2015 3:48 pm
by Edward Stuart
It means the element Tata is available in multiple dimensions
http://www-01.ibm.com/support/docview.w ... wg21454707
Re: Mdx issue
Posted: Tue Sep 22, 2015 5:40 pm
by mincharug.shulft
Thanks Edwart,
How to incorporate can you please help by altering the line that i shared
Re: Mdx issue
Posted: Tue Sep 22, 2015 6:01 pm
by tomok
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.
Re: Mdx issue
Posted: Tue Sep 22, 2015 6:10 pm
by gtonkin
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.
Re: Mdx issue
Posted: Tue Sep 22, 2015 6:37 pm
by Edward Stuart
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