Page 1 of 1

'OldCubeLogChanges'

Posted: Fri Sep 01, 2017 8:21 am
by teamkenji
Hi all,

I have seen the following code used in a TI that I'm trying to understand:


PROLOG TAB:
OldCubeLogChanges = CUBEGETLOGCHANGES('FB Loan');
CUBESETLOGCHANGES('FB Loan', 0);


EPILOG TAB:
CUBESETLOGCHANGES('FB Loan', OldCubeLogChanges);


I have also seen "OldCubeLogChanges' referenced in the 'Generated Statements' Section of the TI Tabs

Can anyone give me a basic run down of what is going on here as I cannot find much to do with the 'OldCubeLogChanges' piece.

Thanks for your time .

Regards

Ben

Re: 'OldCubeLogChanges'

Posted: Fri Sep 01, 2017 9:00 am
by Wim Gielis
It's just the name of a variable.
That variable stores the value of 0 or 1, whether logs should be recorded or not. During the process we tend to disable transaction logging (put it to 0) while at the end of the process in the Epilog tab we restore the initial value (taken from the variable).

Re: 'OldCubeLogChanges'

Posted: Fri Sep 01, 2017 9:37 am
by Elessar
Welcome Ben, congratulations, your 1st post is the 10000s topic in TM1 forum (without subforums)!!
10k.png
10k.png (44.35 KiB) Viewed 3787 times

If you want more information, google about the functions "CUBEGETLOGCHANGES", "CUBESETLOGCHANGES"
The functions change the target cube's logging behavior which is stored in }Cuperpoperties cube, in "Logging" measure

Re: 'OldCubeLogChanges'

Posted: Fri Sep 01, 2017 10:24 am
by Edward Stuart
OldCubeLogChanges is a variable generated by TM1 as part of the wizard, this is why you see it in the generated statements section.

The wider context is around what needs to be logged and when, it is worth reading through the Operations Guide >System and Performance Monitoring > Logging Transactions to delve into this further

Re: 'OldCubeLogChanges'

Posted: Wed Sep 06, 2017 4:13 am
by teamkenji
Thanks for your help guys.

Having come across from EP, This forum is essential reading.


Cheers


Ben