DAXMD DCR: every attribute should have UniqueName property by furmangg

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:
http://connect.microsoft.com/SQLServer/feedback/details/775587/inconsistent-syntax-for-column-references-in-daxmd-for-non-aggregateable-attributes