Undo button does not work

[Toto]

Hello,
I typed in some values in cube view. When I try the undo button nothing happens. When I try another TM1 Server the button works. In security settings logging is activated. What else can it be?

Thanks a lot for your help!!!

Toto

[Steve Rowe]

hi Toto,
Not sure if this is what you mean but, if you are trying to undo selections in the transaction log then you need to actively select the rows in the menu before selecting undo. Just highlighting the row and selecting undo will not do anything.
HTH

[Toto]

Hi Steve,

thanks for your reply. No I did not mean in the transaction log directly. IN TM1 9.5 there is a undo button. So, if you type in "10" in a cell and want to have the value that was in the cell before you should be able to click the undo button. In one TM1Server it works, in another it does not. As I just copied the tm1s.cfg from the server where the undo function is working I wonder which settings could cause this behaviour. Or is it a bug that occurs sometimes?

Thanks for your input!

Toto

[Alan Kirk]

Hi Steve,

thanks for your reply. No I did not mean in the transaction log directly. IN TM1 9.5 there is a undo button. So, if you type in "10" in a cell and want to have the value that was in the cell before you should be able to click the undo button. In one TM1Server it works, in another it does not. As I just copied the tm1s.cfg from the server where the undo function is working I wonder which settings could cause this behaviour. Or is it a bug that occurs sometimes?

From what I've seen of the vaunted and hugely overdue 9.5 undo option (eaaassy John, steeeeady...), it seems to be dependent on the log files rather than on buffering the transactions in memory. (Which makes sense in a way since the latter could cause huge memory blowouts.)

If logging is enabled for a particular cube, then Undo will work. If you turn logging OFF for the same cube (via right clicking on the "Cubes" list and selecting "Security Assignments...") then make a change, the Undo option will no longer be available.

My suspicion is therefore that it's not so much the server that's the issue, but rather the logging status of the individual cubes that you're entering into.