AS2005, MDX: Impact of EXISTING operator - by Michael Barrett

Status : 


Sign in
to vote
ID 126530 Comments
Status Active Workarounds
Type Suggestion Repros 1
Opened 3/12/2006 10:52:28 AM
Access Restriction Public
Primary Feedback Item 124667


When using the EXISTING operator in MDX to have a set of members returned that "exist" within the current query context, the result is only affected by the restrictions applied in the WHERE clause of the query. Restrictions from subselects (or previous CREATE SUBCUBE statements) are ignored, so in these cases the EXISTING operator does not have the desired effect. It is confusing (and a possible source of errors) that subselects - in general - do not establish the current coordinate in the cube, whereas the WHERE clause does. For a more elaborate discussion of the problem, see
Sign in to post a comment.
Posted by Microsoft on 11/20/2007 at 1:12 PM
We hope we can get something into the next release to resolve this. It's not a sure thing at all, but chances are pretty good.,
Posted by Michael Barrett on 6/15/2006 at 4:20 AM
Is this being considered?