DAXMD querying member properties needs better error message - by GregGalloway

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 775748 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/3/2013 7:58:08 PM
Access Restriction Public

Description

This query works fine since we're querying the Customer attribute and the Email Address member property.

EVALUATE
          SUMMARIZE(
            VALUES('Customer'),
            'Customer'[Customer.Key0],
            'Customer'[Customer],
            'Customer'[Email Address]
          )

However, if I query the Email Address member property directly using this query...

EVALUATE
          SUMMARIZE(
            VALUES('Customer'),
            'Customer'[Email Address]
          )

The error message is not very helpful:

Query (2, 11) Column [Email Address] is part of composite key, but not all columns of the composite key are included in the expression or its dependent expression.

The error message isn't helpful especially because it's the same error message you get if you summarize by the name and don't include the key:

EVALUATE
          SUMMARIZE(
            VALUES('Customer'),
            'Customer'[Customer]
          )

I feel that you should create a better error message if you query a member property without the parent attribute. 

I think this is especially important because you have chosen to refer to a member property Email Address of the Customer attribute as: TableName[MemberPropertyName] rather than TableName[AttributeName.MemberPropertyName]. (From what I can tell, you only get the TableName[AttributeName.MemberPropertyName] if there's already another member property with the same name on another attribute.)
Sign in to post a comment.
Posted by Microsoft on 2/10/2013 at 9:36 PM
Hello,

Thank you for reporting this issue. We have changed member property name generation to include attribute name. This will be reflected in a future release. The current error message is reflective of an error in tabular model and member property is part of the multidimensional models.

Regards
Siva