I have two very similar reports with list boxes and pivot tables.
On the list boxes and pivots I have "Preserve Scroll Position" set to true.
On list boxes...
On report A this is respected so when the users scrolls down, the scroll bar stays in the selected position.
On report B this is NOT respected so when the users scrolls down, the scroll bar flips back to the top...
My pivot tables ar displaying the same symptoms on the respective reports...
I have ran through the User Settings / Document Settings and Object Settings to see if I can see a difference between the two reports but have found no differences.
Is there are different setting which could cause the two reports to work differently?
do you have triggers (actions), if you change a sheet, which use formula (i.e. =Year(Now()). If yes I have the same problem and it is a known bug for Qliktech. It's not clear, when this bug is solved.
As a workaround I create variables in the load-script which get filled with my desired values and I use them in my actions.
do you have triggers (actions), if you change a sheet, which use formula (i.e. =Year(Now()). If yes I have the same problem and it is a known bug for Qliktech. It's not clear, when this bug is solved.
As a workaround I create variables in the load-script which get filled with my desired values and I use them in my actions.
I have just seen your entry which may help me, because I have the same behaviour in a table. It does seem that the table is having to do a repeated calculation, which un-sets the scroll position. At one point I was using the ABOVE() function in an expression, but I have removed this.
But .... please can you explain what you mean by triggers ? My Table is based on date selections, but it may produce a large number of rows.
in my case it was a simple select box and it wasn't combined with a calculation.
Triggers are actions that get executed i.e. if you change to another sheet and you want to make a selection without user interactions. In my case I selected the current year as shown in the attached picture. To avoid this problem I store all the values I need in variables and then I don't have that kind of problem.
