Hello everyone,
I think i found a bug on paralleleperiod function

When i ask a paralleleperiod(year,1,time.currentmember) all works fine
except in one case :
when the time.currentmember is a month and the year before doesn't start by
january

An example :
My time dimension begins in april 2002
i ask paralleleperiod(year,1,TIME.2004.april), it returns TIME.2003.April
if i ask paralleleperiod(year,1,TIME.2003.april), it returns
TIME.2002.JULY!!!!

To avoid this problem i make a test in my calculated member : if y am at
year level i ask paralleleperiod(year,1) and if i am at month level i ask
paralleleperiod(month,12)
It works but i fear the day when i will have time dimension with missing
month!

Anyone can tell me if this bug is known?

Thanks

Unfortunately, this is not a bug, it is the documented behavior.
ParallelPeriod does not have any real time intelligence, it works by using
the relative position (maybe things will be different in SQL Server 2005 ).
So when you ask for ParallelPeriod of April 2003, the function takes the
ancestor of April 2003, which is the year 2003. It then takes the sibling of
2003 that lags by 1 , which is the year 2002.
Finally, since April is the fourth child of 2003, it takes the fourth child
of 2002, which is July.
For ParlallelPeriod to work as expected, the Time dimension must have a
regular structure, with no missing members.
HTH,
Brian
www.geocities.com/brianaltmann/olap.html







"Cymryr" wrote: