topic Re: How to fix the pivot table width in QlikView

How to fix the pivot table width

udaya_kumar — Mon, 08 Jan 2018 13:46:54 GMT

Hi,

I have created an adhoc report in QlikView where the users have the option to select the dimension and expressions given in the listbox.

When they select the dimensions and expressions, those will be enabled by using the conditional enabling of dimension and expression in pivot table.

I have a fixed width for the sheet to place the objects.

When i select more dimensions, then the pivot table goes out of the fixed width in the sheet.

So how to restrict the table to have fixed width with scrollbar to scroll to the right?

Re: How to fix the pivot table width

Anil_Babu_Samineni — Mon, 08 Jan 2018 13:51:15 GMT

Can you enable this option?

Re: How to fix the pivot table width

udaya_kumar — Mon, 08 Jan 2018 13:52:43 GMT

Hi Anil,

I have removed that Size to Data option, still the table goes out of the fixed width.

If i select more dimensions and one expression, it goes out of the range given.

Re: How to fix the pivot table width

marcus_sommer — Mon, 08 Jan 2018 13:52:58 GMT

The expression-columns from a pivot could have a scrollbar but not the dimensions. The meant you will need to limit the max. number of dimensions within your pivot - maybe by adding an additionally counter to your conditions like:

... and getselectedcount(YourDimensionChoice) <= 6

- Marcus

Re: How to fix the pivot table width

Anil_Babu_Samineni — Mon, 08 Jan 2018 13:54:35 GMT

Till how many you have added?

Re: How to fix the pivot table width

udaya_kumar — Mon, 08 Jan 2018 13:57:40 GMT

Oh.

I have more dimensions available for user to select (43 dimensions) and 6 expressions.

So you are saying, only the expressions will have scroll bars, not the dimensions.

Re: How to fix the pivot table width

marcus_sommer — Mon, 08 Jan 2018 14:06:32 GMT

Yes, dimensions won't have a scrollbar. But in total 49 columns are far more than useful for an user and such big tables could require a lot of resources and it's not uncommon that they will end with an out-of-memory message. Therefore a restriction on the number of columns (and rows, too) and/or maybe a split into several objects might be helpful.

- Marcus