Inconsistent behavior for DAX queries if a NameColumn is specified - by Gerhard Brueckl

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<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 775561 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/2/2013 1:56:57 AM
Access Restriction Public

Description

If the KeyColumn and the NameColumn of an attribute are based on different column the DAX SUMMARIZE()-function requires both columns to be specified in the query. This makes the query more complex and unreadable (using [MyAttribute.Key0] and [MyAttribute]). Also these Attribute Keys show up in the final result exposing internal keys (surrogate ids, etc.) to the end-user what may not be intended

If KeyColumn and NameColumn are based on the same column, everything works as expected without the need to specify "KeyX" for every column

similar to MDX, also in DAX the end-user should not need to be aware of the internal data structure (keycolumns, namecolumns, etc.) - this should all be handled internally without the users awareness
Sign in to post a comment.
Posted by Microsoft on 1/20/2013 at 11:51 PM
Hello,

Thank for your feedback. This behavior is the current design. Due to the current DAX semantics and for the ability for clients to query the key column, we expose the metadata via CSDL-BI. Clients are expected to interpret the CSDL-BI metadata and form the appropriate DAX query for the right results.

Regards
Siva