Problem using the .&[member] expression

  • Hi all, I need some guidance on this difficult problem.

    Version: SQL Server/SSAS 2012

    I have this calculated measure that looks like this:

    CREATE MEMBER CURRENTCUBE.[MEASURES].[California - Total Stuff]

    AS (

    [Property State].[Property States].CurrentMember,

    [Property State].[State].&[CA],

    [Measures].[Number of Stuff] ),

    FORMAT_STRING = "#,#",

    NON_EMPTY_BEHAVIOR = { [Number of Stuff] },

    VISIBLE = 1;

    It is working perfectly. In the Calculation Tools, Metadata Tab, each member is referenced by "&" so when I drag them into the expression, the selected member comes out as [Property State].[State].&[CA].

    My problem is that in another project file, same environment, same dimension and hierarchy, the members are not referenced by the "&" symbol. in the example above it looks like [Property State].[State].[CA] when I drag it into the expression. This is also the case when I mouse over on each member.

    On the example calculated measure above, I've written it in both ways

    [Property State].[State].&[CA] AND also tried [Property State].[State].[CA] but none of them work.

    Is there a property in the dimensions that I am missing on the other project file maybe?

    Please help. Any assistance is greatly appreciated.

    Regards,

    Mike

  • The ".&[]" notation usually indicates a tuple. If the syntax generated does not contain the ampersand, it means that it is not an actual tuple but a level within the attribute hierarchy (i.e. not the lowest level).

  • Thanks for the reply Martin, I really appreciate it. Unfortunately that is not the case. In the first example, State is also a level in the hierarchy. the members come out as &CA, or &San Francisco (City level). Just strange that in the other project file, it is not behaving the same.

  • Are you not maybe using a user-defined hierarchy in the one system, and the attribute hierarchy in the other?

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply