Anyone out there disturbed by the fact that the
nonemptycrossjoin() automatically filters out calculated
members?

I have some fairly large dimensions that often get nested
by end users, causing crossjoin() operations in the front-
end tool we are using. The tool also has a "filter null
rows and columns" feature that causes a filter() to be
wrapped around the crossjoin(). The tool vendor has
implemented a feature to optionally use a nonemptycrossjoin
() in these cases, which helps a lot with performance.
But as soon as this is done, calculated members are
automatically filtered out. Most troubling when the users
have the [Measures] dimension as part of the nesting since
it typically contains a host of calculated members. But
it also happens with calculated members in other
dimensions.

Has Microsoft acknowledged this as a problem that needs to
be fixed/addressed? Yes, it says in BOL that this is the
behaviour of the nonemptycrossjoin() function, but that is
simply documenting a bad functional design. Any thoughts?

Dave Fackler

"Dave Fackler" <davef (AT) intellinet (DOT) com> wrote

Dave,

While this is the "By Design" behavior for NonEmptyCrossJoin function, we
are getting feedback, that in some cases (like in your example), it is
desirable to keep calculated members. We are looking into making it possible
in the next version.

Thanks,
Mosha.

--
==================================================
Mosha Pasumansky - www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================

Hi Dave,
you are not the only one experiencing this.
I have seen several postings (going back as far as 1st
half of 2002) which relate to this issue.
I also have the same problem with certain combinations of
filters, calculated members and dimensions.

(See my recent posting Flatliners)

It does seem as if there is no current solution to this.
I have heard that PTS would have to be redesigned to
solve this ... and that this might happen in 2006.

It would be good to know when exactly, since this is only
hearsay.

I'd be glad to know which frontend you are using, since
we currently use excel 2002. (Which does not give an
opportunity to use NCJ as far as I know)

TIA
Lutz