DAXMD DCR: every attribute should have UniqueName property - by GregGalloway

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.

Sign in
to vote
ID 775973 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 1/7/2013 8:02:22 AM
Access Restriction Public


It is very helpful that the Scenario attribute in the Scenario dimension in Adventure Works has a Scenario[Scenario.UniqueName] column in DAXMD. That is very helpful in building an SSRS report using a DAX query and passing in parameters. For example, hooking an SSRS report into a PerformancePoint dashboard is done naturally by passing in MDX unique names to the SSRS report parameters.

However, it appears the only time the .UniqueName property shows up as a column is if it's a dimension with a single non-aggregatable attribute with calculated dimension members defined in the MDX script. I feel that every attribute should have a .UniqueName property column that's hidden.

Another issue has been opened about the fact that Scenario[Scenario.Key0] doesn't exist. I believe this is because there's a calculated member defined on that attribute in the MDX script (and thus there's no key for calculated dimension members). Still, Key0 should be there, in my opinion. The other issue I refer to is:

Sign in to post a comment.
Posted by Microsoft on 1/21/2013 at 12:21 AM

Thank you for the feedback. Currently we expose the tabular metadata for a multidimensional model via CSDL-BI which is the discover. We expect clients to retrieve the metadata and form appropriate DAX query. In order to keep the right level of metadata and performance considerations, we only have UniqueName exposed as key columns for DAX query. Hence we are not exposing UniqueName for all the columns. This is the current design.