I am using the classic Dates dimension with a Dates.Days Attribute Hierachy
and a Dates.DateFiscalCal User defined Hierachy.
When I use the Hierachy drilled as Row Headings all the formulae work fine
and the .name of the Dates.DateFiscalCal.CurrentMember is always correct on
each row.
However when I move that Dates.DateFiscalCal Hieracy to the Filter of the
report (in MDX Script debug etc), and select one of the dates that worked OK,
now all the formulae give wrong answers corresponding to random wrong values
for Dates.DateFiscalCal.CurrentMember not beig set to the filtered value.
Amazingly, this is fixed by moving the Dates.Days Attribute Hieracy to the
Row headings where it gets filtered correctly and forces the
Dates.DateFiscalCal.CurrentMember to the correct filtered value on all the
row cells.

This is real weird but consistent after 2 days of permuting around it.
Anyone seen behavior like this?

--
Mike L

Take a look at the thread.
http://www.webmasterdev.com/showthread.php?t=617585

There are a few of us struggling with it.


--
CliffordS