SSAS 2005 Add Business Intelligence Time Calculations adds another hierachy
to the Dates dimensions for calculated members. I found that these
calculations worked OK unless another hierachy of the same dimension was
moved to the filter of the MDX. Then a calculated member to find the
..CurrentMember.Name of that hierachy was never correct for the lowest level.
I verified this MDX "bug" on a very simple dimension by adding a calculation
hierachy within the dimension and adding the .CurrentMember.Name calculated
member. This could not discern the correct value when the main hieracy was
used as a filter at the lowest level.
As soon as I put exactly the same calculation on another calculation
hierachy on a differerent dimension, the results were always correct.
I use my dimension calculated members as filters all the time in my reports
so I need them to work to complete my upgrade from AS 2000. I will report
any related issues if I find them.
Anyone else finding this problem?
--
Mike L

I also found errors if I put the Dimension Calculated Members under a User
defined hierachy - it had to be an Atttribute Hierachy.
--
Mike L


"Mike L" wrote:

Are you using SP1?
Microsoft claims that they fix this problem in SP1. There was a thread a
month or so ago, where Microsoft claimed that they fixed this problem in
SP1, but myself and other people did not agree. I do not use business time
intelligence, but I have very similar logic for my time intelligence and I
tested in SP1 - it does not work.I am still using my workaround, where I
duplicated lowest level of time dimension (Year-Qtr-Mth-Day-DayKey). DayKey
level is not visible and because in this structure day is not the lowest
level, it works. It is not a good workaround as there definatelly
performance hit on cubes, but for now it works. I do hope that Microsoft
will fix this in some post SP1 hot fix or at least in SP2. But to do this,
first of all they have to acknowledge that this is a bug! I follow this
group closely and so far they did not agreed that this is a bug.
I would love to hear from MSFT people on this issue.

Regards,






"Mike L" <MikeL (AT) discussions (DOT) microsoft.com> wrote

I am definitely using SP1 - good to hear that others are seeing the issue.
It is definitely a fault on the lowest level of the filter hierachy and it
fails on any hierachy (the .CurrentMember is wrong). I appreciate your work
around but try moving the Dimension Calculated Measures to an attribute (not
user defined) hierachy on a different dimension entirely. That weird
workaround fixed it for me without the performance hit.
The .CurrentMember value being wrong under a simple one member filter is
such a basic and serious fault (of course it worked in AS 2000) that it must
be being fixed at the moment (I hope).
Thanks for the feedback
--
Mike L


"Vimas" wrote: