TM1 Forum

Sounds a good idea.

I haven't been to it for years, but the Gun, on Coldharbour, is nearby, has the most amazing view, and has been done up - http://www.thegundocklands.com/index.html

Cheers
David

Actually I would say that TM1 (and the tools which are 'tributes' to TM1) are the exception not the rule. If you have to run a process of some time to get your consolidations then changing them doesn't change history. I can confirm that for Express and Essbase. Just reminds me how far back I go in t...

Interesting idea. I often find it necessary to have YTG (though I haven't been calling it that) if I am feeding from a YTD-based cube to a current month-based cube, and it would be quite neat to pick it up for the moving average. But if that isn't required I think I'd stay with the FY less YTD as I'...

We've done a refinement of the IF approach using an Excel macro to turn the =DBSW( formulae into comments and back to active formulae. Less cluttered than the IF and nice and quick.

Errr..... No. But when I did, I got the same behaviour you saw - it appears the rules parser can't handle squiggle dimension names in the [dim:'Element'] syntax. B***er. And also, looking through our standard demo setup, which was touched by SPF many years ago, I see similar rules to those John H de...

However it got there, wouldn't it be better changed from

[] = S:if( ~ !}GROUPS @= 'ADMIN', 'WRITE', STET);

to
[}GROUPS:'ADMIN'] = S:stet;
[] = S:'WRITE';

?
I do like to minimise IF tests as far as possible...

I've done this a number of times without stepping away from the 2 lump (Year separate from Month) time structure. It's not too bad, but you need a cube for the workings. The approach is: 12 Month Moving Average = Current YTD plus Prior full year less Prior year YTD Drop those into a workings cube, p...