Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content
Announcements
Gartner® Magic Quadrant™: 15 YEARS A LEADER - GET THE REPORT
cancel
Showing results for 
Search instead for 
Did you mean: 
evis_ka
Contributor
Contributor

Pivot Table Randomly Resizing and Ignoring Toggle Button – Anyone Experienced This?

Hi everyone,

we’re experiencing a strange and recurring issue in one of our QlikView applications, and I’m wondering if anyone else has seen something similar or has any suggestions on how to prevent it.

We have a pivot table that contains a large number of metrics. Since expanding it to full width by default would be impractical, we’ve set its width manually to around 750 pixels. Above the table, we use a toggle button (styled as a collapsible/expandable arrow) that switches a variable vMaximize. Based on this variable, the table either expands to full width or stays collapsed – this setup works well and allows users to control the view as needed.

However, every few months, the application seems to "break" on its own. The pivot table suddenly expands to full width permanently (e.g., around 4000 pixels), the toggle arrow either disappears completely or stops responding, and when we inspect the object, the fixed width has changed – no one has touched the application or edited the layout in the meantime. It's as if QlikView silently overwrites the original object settings.

Has anyone else encountered this behavior?

  • Is there a known bug or cause behind this kind of spontaneous layout change?

  • Could it be related to server caching, corrupted object state, or QVW auto-save behavior?

  • Is there any way to lock object dimensions or prevent QlikView from changing them unexpectedly?

Any insights or suggestions would be greatly appreciated – this issue is quite frustrating since we have to manually fix the layout every time it happens.

Thanks in advance!

Eva

Labels (1)
1 Reply
marcus_sommer

It may related to the existing data because the pivot doesn't mandatory store the view you have within the UI else it stores the relation to the underlying data.

At least the expanding/collapsing of the dimension-values relates not to the shown values else to the field-value-index and if the data are changing respectively coming in a different order the view will change. I could imagine a similar behaviour by other settings, too.

OSZAR »