strange excel behaviour

[stingo]

Hi all,

I have this strange behaviour when opening Data entry forms in TM1.

For some of the excel forms in my environment, after the recalculation (via TM1 Button) the excel puts as active the first cell after the "view" zone of the DEF.

This is an issue for the big sized forms because the user has to scroll up all the thing (users are lazy).

Some notes:

I'm using TM1 9.4.1
there is apparently nothing different about forms with the "strange" behaviour and the "normal" behaviour ones.

has someone incurred in the same? How to solve it?

Thanks in advance for the answers.

[lotsaram]

As far as I'm aware this is normal behaviour for active forms and it more or less makes sense. When an active form is refreshed TM1 doesn't know in advance how many rows will be in the form post refresh. During the refresh all rows in the data range except the first are deleted then re-inserted. TM1 just takes the easiest and probably most sensible option of making the 1st row of the data range the active cell after a refresh as that is the only row guaranteed to be there.

As the UI in this case is Excel and not TM1 Web then why not replace the action button with a VBA button. Then it would be easy to cature the active cell (or better the relative offset of the active cell from the origin of the active form) and set the active cell to the same relative position after calling the TM1Refresh macro.

[stingo]

As far as I'm aware this is normal behaviour for active forms and it more or less makes sense. When an active form is refreshed TM1 doesn't know in advance how many rows will be in the form post refresh. During the refresh all rows in the data range except the first are deleted then re-inserted. TM1 just takes the easiest and probably most sensible option of making the 1st row of the data range the active cell after a refresh as that is the only row guaranteed to be there.

As the UI in this case is Excel and not TM1 Web then why not replace the action button with a VBA button. Then it would be easy to cature the active cell (or better the relative offset of the active cell from the origin of the active form) and set the active cell to the same relative position after calling the TM1Refresh macro.

so, if this is the normal behaviour, why in other forms the behaviour is exactly the opposite?

[qml]

Are they ALL Active Forms? Maybe the other ones are good old-fashioned slices?

[stingo]

Are they ALL Active Forms? Maybe the other ones are good old-fashioned slices?

all of them are active forms and all of them are made the same way.