TM1 report flickering after upgraded from 9.0 to TM1 101.1

[Firefly007]

I have old report which is runing on 9.0 which does update to cube and does varios things like copying , unlock, locking. i dont see any flickering or transaction happening in 9.0 .

When I upgrade same report to TM1 10 i see there is degradation in performance and i can see flickering on the screen the VBA transaction like copying etc...
is there is a way we can fix this issue ?

I tried Application.ScreenUpdating= False even this doesnt work.


Could any one help me understand if there is a change in TM1.xla file compared to TM1p.xla in TM1 10 version.?

[tomok]

Could any one help me understand if there is a change in TM1.xla file compared to TM1p.xla in TM1 10 version.?

So, you want to know if there have been any changes to the Excel add-in in the last 5 years? I think it's safe to assume there have been a few.

[Firefly007]

Thank you for the reply. Is there is a work around for this issue?

[lotsaram]

Thank you for the reply. Is there is a work around for this issue?

I think its safe to say no. You can raise a bug report with IBM. You won't be the first for this issue but it seems unlikelly that anything will happen since nothing is broken there is just a performance degredation due to screen updating. Somewhere in 9.4 or 9.5 it seems an application.screenupdating=true seems to have found its way into the recalculate functions within the perspectives add-in.

[jrizk]

From 9.5 (I think) screen updating was turned on in the TM1RECALC and TM1RECALC1 calls in tm1p.xla.

Application.ScreenUpdating = False has no effect as when the recalc calls are made ScreenUpdating is switched on - hence the screen flicker.

Not sure about 10.1 but up to 9.5 TM1RECALC and TM1RECALC1 were just functions that made calls to TWEVRECALC and TWEVRECALC1 respectively.

Use:
Application.Run ("TWEVRECALC") instead of TM1RECALC
Application.Run ("TWEVRECALC1") instead of TM1RECALC1

with Application.ScreenUpdating = True/False where required.

[Firefly007]

Thank you Riz!

This change made a significant improvement i dont see the flickering any more.

This formula TWEVRECALC i have not seen in the Tm110 IBM documentation.

Can you please help me with more information.

1. What is the difference between TWEVRECALC1 and TM1RECALC1.
2. What is this TW EVRE CALC1 do when we run a report. Will this effect to write back data to cube?


Thanks
Firefly

[jrizk]

1. What is the difference between TWEVRECALC1 and TM1RECALC1.

There is no real difference between TMEVRECALC1 and TM1RECALC1. TMEVRECALC1 is the function that performs the recalc - TM1RECALC1 just calls TMEVRECALC1. I haven't investigated but I think TMEVRECALC1 is a function in one of the dll's that tm1p.xla uses - not sure which one though.

2. What is this TW EVRE CALC1 do when we run a report. Will this effect to write back data to cube?

TMEVRECALC1 does what TM1RECALC1 does and handles write back the same way (assuming you mean using recalc with the DBSW/DBSS functions to send data to the cube).

[Firefly007]

Will it support the funtionality DBRW formulas while writing back to cube in this case?