DAXMD: Supress Member Properties - by Teo Lachev

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.

Sign in
to vote
ID 761432 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 9/6/2012 6:01:35 AM
Access Restriction Public


IMO, I don’t see a good use of exposing member properties, not to mention that hiding them will require changes to the cube to hide the attribute relationships just to support Power View. 
Sign in to post a comment.
Posted by almaplayera on 12/6/2012 at 6:21 PM
huh. i came here to request the exact opposite.

consider the "Customer" dimension of the AdventureWorks "Direct Sales" perspective:

1) wouldn't a Power View table visualization with two fields, "Customer" and "Email Address", be a perfectly reasonable use case?

2) why would i prefer to enable the attribute hierarchy for the "Email Address" field?
* it's not an attribute by which users will dimension cube information
* disabling the attribute hierarchy will improve processing performance
* in excel, with "customer" in the rows area, query performance will be much faster with "Email Address" as a member property rather than as a hierarchy / field

so, what am i missing? why wouldn't i want the "Email Address" member property exposed in DAXMD / PowerView?
Posted by SIN420 on 9/24/2012 at 1:26 PM
I agree 100%