strange pivot table behaviour

[pkelly]

I have a pivot table which is presenting strange behavious with regards to the scroll bars and I was wondering if I had accidentally turned on (or off) a setting somewhere to cause this...

Normally when scroll bars are present, you drag the scroll bar down and it stays where you stopped...

For example, if you had a list of accounts and scrolled down half way on the vertical you would be @ the M's..

What this one is doing is let me scroll down half way (and I can see the M's) but, as soon as I release the scroll bar it automatically scrolls back up to the to top.

Same applies to the horizontal scroll bar...

Is this a setting somwhere?

[pkelly]

Some additional detail...

Have searched through the forum on this and the suggested fix relates to the "preserve scroll position" checks in either the user preferences or layout options of the pivot table...

Just one problem - I cannot see this option...

I am on version 8.2 - is this option hiding somewhere else...

[pkelly · Accepted solution]

Some additional detail...

My Pivot Table window title contains the following...

=varReportViewName & ' - Customers with no iPack Order placed between ' & Date(min(soi_ReleasedDate),'DD/MM/YYYY') & ' and ' & Date(Now(),'DD/MM/YYYY')

If i remove this and just type in say Test the scrolling reset issue disappears i.e. the pivot preserves the scroll position...

Why would this affect the pivots ability tp preserve its scroll position?

[#4]

I guess you would have fixed the problem by now...

I had same issue and was browsing thro forum and came across this thread... I too had now() as part of my chart title 🙂

In case someone has same issue, replace now() with today() or something similar... "now" keeps ticking!

[pkelly]

Yes, since my post we have upgraded to version 9 where we can utilise the preserve scroll position

[#6]

Hi guys...

I'm on v9 and I'm getting the same behaviour... when I scroll down, after about a second it bounces back up to the top of the table.

This happens whether or not there is a formula in the caption bar, or whether or not I use the preserve scroll position check box....

Am I missing something??? Mike

PS most of my tables use formulae in conditional displays and/or dimensions settings but I can't see why this would affect the scroll bars...

[syed_muzammil]

Hi,

Check if you are using a now() function in your expressions. Now() causes your expression to be revaluated for every second which results in the table refreshing and going to its original scroll position. Instead use today().

Regards,

Syed.

[#8]

Hey Syed... now() was the culprit...

I had a variable to store the current day/time being set on a sheet activation trigger.

As it was tucked away in a sheet activation trigger (incidentally not the sheet with the table) so I didn't think the Now() would be evaluated every second... like... I thought it would only be triggered when the sheet was activated.

Anyway... I didn't really need it anyway so it got the chop! Thanks, Mike

[#9]

I was having the same issue with filter boxes. Removing now fixes it

[#10]

When using nprinting reporting module, using the now() function can also result in rather strange behavior.

I had used the now() function not in the chart title, but in the chart expressions. Specifically, in a set expression within a chart formula, limiting the number of years of data which Qlikview was required to compute in the nprinting field iterations.

The charts I'm handling hold some expressions which are quite heavy for the processor. Due to qlikview refreshing the chart every second, nprinting was seemingly unable to fetch the charts in time. Eventually this resulted in a loop crashing our qlikview server (eventid 300 and 1000 in windows eventlog).

Ironically, the set expression which I had added in order to speed up the calculations had now actually slowed the nprinting report down to a crawl.

I was able to relate the problem to the now() function as I could not scroll down in the charts which nprinting was supposed to fetch. Googling for this issue led me to this post.

Replacing now() with today() solved my issues.