Hi all I have the following hierarchy in my [Organization] dimension: Area SubArea CountryGroup Country So far I did not find a way to create a data source query that has a field that can potentially contain members from multiple levels on a user-defined hierarchy (natural hierarchy). In the XML definition of of the created data source field, the level of the field is contained (for example Level="[Organization].[SubArea]". The idea is to create a drill-down on that field by calling the same report and passing the current member of the Organization dimension as a parameter regardless of the level of the current member and show its children. I could achieve this behavior on a parent-child (PC) hierarchy. For example we also have an account hierarchy in the same cube. Regardless of the level of the account, the field corresponds to [Account].[CoA] (dimension name [Account], ParentName = [CoA]) I would like to be able to use intrinsic member properties of the current member of a user-defined hierarchy over all levels. I want to use them to group my rows or columns in the tablix. As a workaround I created calculated members contain these members properties as a string (which not really a good thing). For example: WITH MEMBER [Measures].[Organization_UniqueName] AS Organization.Management.CurrentMember.UniqueName WITH MEMBER [Measures].[Organization_Level] AS Organization.Management.CurrentMember.Level.Ordinal I would by far prefer a method that uses DIMENSION PROPERTIES in the MDX query. and not to create these artificial calculated members. Can someone help me out?

Hi Stefan, Can I know how many Members are You Looking at Each Level ? Area SubArea CountryGroup Country If its well below 100- there wont be any Reporting Performance Issues when you Query MDX on the Cube. As you Require Level,Uniquename has to be a member Property rather than using a Calculated Member ..You Can Achieve this by Creating a View or Changing the DSV in your Cube and making this as an Attribute. For Ex : Add a Level Column to all the 4 Table and Assign a Default Value. Similary if you want UniqueName Create a Varchar field and Populate the Data While doing a Dimension Load. Usually UniqueKey will be [xxxx].[yyy].[&DatabasePrimaryKey] which can be an Update statement on that Column. Kindly Consider Design Changes do achieve the Above. Rakesh M J Dont forget to mark it as Answered if found useful MCTS,MCITP,MCSS http://myspeakonbi.blogspot.com/