Home Dashboard Directory Help
Search

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


Status: 

Closed
 as By Design Help for as By Design


1
0
Sign in
to vote
Type: Bug
ID: 775561
Opened: 1/2/2013 1:56:57 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

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
Details
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
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
Queries.txt 1/2/2013 389 bytes