<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><blockquote type="cite"><div><blockquote type="cite">On Thu 03 May 2012 05:27:34 PM WEST, Pedro Alves wrote:</blockquote><blockquote type="cite"><blockquote type="cite">Is it supported without ussing calculated (aggregated) members?</blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Where <set> works.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">where (<member>,<member>) works<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">where ( <set> * <set> works but this isn't a very optimal approach.</blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I feel I'm missing something very very obvious<br></blockquote></blockquote><blockquote type="cite"></blockquote></div></blockquote><div><br></div>Pedro you may be missing something obvious but I'm not sure what it is.<div><br></div><div>Remember that in MDX:</div><div><ul class="MailOutline"><li> ( ... ) is the syntax for a tuple. Members must be from different hierarchies.</li><li>{ ... } is the syntax for a set. Elements in the set must be members (or tuples) with the same dimensionality.</li></ul><div><br></div><div>You can write</div><div><br></div><div>WHERE {h1.m1, h1.m2} * {h2.m1}</div><div><br></div><div>or </div><div><br></div><div>WHERE CROSSJOIN({h1.m1, h1.m2}, {h2.m1})</div><div><br></div><div>or</div><div><br></div><div>WHERE {(h1.m1, h2.,1), (h1.m2, m2.m2)}</div><div><br></div><div>and they are all valid and equivalent.</div><div><br></div><div><br></div><div><blockquote type="cite"><div>Am 03.05.2012 um 18:30 schrieb Pedro Alves <<a href="mailto:pmgalves@gmail.com">pmgalves@gmail.com</a>>:<br><br><blockquote type="cite">Bah - from <a href="http://jira.pentaho.com/browse/MONDRIAN-555">http://jira.pentaho.com/browse/MONDRIAN-555</a> I take it it's a <br></blockquote><blockquote type="cite">no? :S<br></blockquote></div></blockquote><div><br></div><div>No, that bug only relates if you have ancestor and descendant members in the same set. It will affect totals to a value that is arguably wrong, but the slicer should still work.</div><div><br></div><div>Julian</div><div><br></div></div></div></body></html>