Vizlib Pivot Table Changelog

When the users selected between 2 to 6 dimensions in their application, the Measures title changed its position from column to row.

The Preserve white space option was not working for old reports after upgrading the version from 3.9.1 to 3.10.1.

Color formatting was not working.

The scope of the Vizlib Freemium license has changed. Please, see the Pricing and Subscriptions FAQ to see how the changes affect your use of Vizlib Pivot Table.

When the customers used Vizlib Pivot Table inside Qlik Container and wanted to access the applied bookmarks, the tab quickly switched to a different tab and the Access Denied error message was displayed.

A formatting mismatch was identified in the Pivot table.

The attribute expression switch has been introduced.

The switch is available only for newly created objects or for objects with migrated attributes. The switch has two states:

• Enabled - Indicates the expression is evaluated once for the whole extension. Use this whenever the expression allows.
• Disabled - Indicates the expression is evaluated once per cell. Use this only when necessary since it may affect the performance.

Measure fields with the attribute switch:

• Measure / Border - Custom / Border Size
• Measure / Font size - Custom / Size
• Measure / Font style - Custom / Bold font style if
• Measure / Font style - Custom / Italic font style if
• Measure / Font style - Custom / Underline font style if
• Measure / Font style - Custom / Shadow font if
• Measure / Representation - Indicator / Indicator threshold

When users expanded Pivot Table rows, the software displayed the following error message: Your quota limit of {0}MB was exceeded. You loaded {1}MB. Reduce your data within this application or buy additional capacity.

When users changed the measure representation type, the software displayed the JSON parse message with -32700 error code.

Software performance was slow after users transformed a regular Qlik Table into Vizlib Pivot Table.

The Time Out error occured when the user selected the Expand All option.

When the software displays the error message as in bug ID VIZ-14423, insightsoftware recommends you manually trigger the migration process for the hypercube attributes by following the instruction:

1. Duplicate the sheet where the corrupted Pivot Table is present (as a backup sheet).
2. Go to the Property Panel for the Pivot Table > Pivot Table Settings and click the button Migrate attributes button.
3. Check for errors in the browser's console log and make sure everything works as before the migration process, for example colors or values.

If the Qlik Sense Error The request exceeds the memory limit continues to occur after expanding the rows, consider that there may be changes required to your data model.

If the QS error doesn't occur, follow the same migration steps for the original object.

The label for the calculation field for dimensions and measures in the Property Panel has been renamed from Calc. Condition to Show column if.

For measure font style section in the Property Panel:

• The Bold font style label renamed to Bold font style if.
• The Italic font label style renamed to Italic font style if.
• The Underline font style label renamed to Underline font style if.
• The Shadow label renamed to Shadow font if.

Performance improvements. In this latest release we have fixed several performance issues that customers experienced. The improvements will help to improve the development and user experience of the Vizlib Pivot Table.

Export to Excel dimension column width doesn't replicate Qlik. When you have indent rows set to off, the exported dimension row column width would not be calculated correct. With this release we have solved for all export inconsistencies regarding dimension width.

Export Null cells background color are wrong. Some users experienced an issue when using measures which had null values within them. The exported color would result in white as a result of the color not being passed over to the formatted excel.

Text using expressions to define colour by dimension.

Line in the release for the Pivot Table v3.6.0 you are now able to color by expression the text in dimension headers.

Re-ordering fields in pivot table/pivot table wizard.

Reordering fields in the wizard now reflects the changes in the property panel for the Vizlib Pivot Table.

We have also made changed to the way Totals are displayed and interacted with in Edit mode of the qlik app. There is now a switch called 'Remember totals' which, when selected remembers the toggle options of showing totals for dimensions.

This is controlled via the property panel and in the Setup/Edit wizard.

Also note that the options 'Total position' is now editable regardless of if 'Show all totals' is toggled on or off.

Finally, you can also use the Vizlib Pivot Table when using calculated fields.

Formatted Export to Excel should reflect the result on screen.

A default option is now implemented which will eventually be the default method of exporting to Excel.

Export column width has been implemented to ensure consistency when exporting your Vizlib Pivot Table to Excel from Qlik.

Add Measure & Dimension Title (Supports HTML) option to the pivot table.

Like in the Vizlib Table where you are able to have HTML support for Headers, the Vizlib Pivot Table has this functionality as of this release.

The Pivot Table allows to change the label (with HTML support) for the HEader label and Label (aka pill).

Add "Rules" indicator range to the Pivot Table Indicator option.

Line in the Vizlib Table v3.22.0 release you can now use advanced rules to calculate your pivot table indicator ranges.

The context menu overlaps the export icon. In Qlik Cloud, the Pivot Table's context menu (on hover) overlapped it's ability to select the export to excel/wizard option.

Difference in loading between different cell heights.

Comparing the performance between a Vizlib Pivot Table with a cell height of 32px and another with 16px the larger cell height (32px) performed better than the smaller cell height (16px).

This was impacting initial loading and scrolling times.

Cell borders disappear when scrolling vertically through huge data. When a lot of data is in the Vizlib Pivot Table and the user scrolls, the cell border color disappears.

Expression driven color calculations for Dimension rows and columns

You can now change the row and column colors using an expression to provide more than just one distinct color output. Simply add an if() statement (for example) to the 'Background color' feature under the dimension you want the styling to be applied to. You don't need to specify if the color should appear on the column or row orientation, we automatically apply that for you.

This means you can achieve results like the below image without needing to specify the name of the value which was required in the previous solution, 'Dynamic Styling'.

Please be aware of the original 'Dynamic Styling' feature will be deprecated and no further improvements will be made to this feature thanks to the implementation of this release.

Note: This dynamic styling option is calculated on the row level, therefore if you have an extensively large pivot table with many rows or columns of data, you may encounter some performance decreases. Encountering this performance decrease is low and won't be noticed in most Vizlib Pivot Table's, for those users who have many rows of data, they could experience some performance issues. A feature will be implemented in the next release to allow for distinct or dynamic color calculations.

Improve scroll bar behaviour in Vizlib Pivot

To keep your Vizlib Pivot Table clear of any distractions we have implemented the a 'hover to show' scrollbar. This will keep your data free of distractions.

Scrollbar

No Scrollbar

Export to excel in Qlik Saas isn't working. In Qlik SaaS if you have not removed your Custom Hypercube from the Pivot Table then when trying to download the data, you would be presented with this modal..Because of this we have created a custom popup that will allow you to download the .XLSX file (but limitations may apply depending on the size of the data you are trying to download).

In this popup, we have implemented Vizlib's first 'Error Code' which you can look up on our documentation page to learn more about the issue and how to rectify it. Please look here for all information about the error code.

Export to Excel displays incorrect measure format based on the order of the measures in the Column Definition. When using Formatted fast export of data, the exported report has the incorrect format as opposed to the chart. A cause for this incorrect display appears from the order of the measures displayed in the Column Definition.

Scrolling on iPad isn't working unless we use the scrollbar. The scrollbar would stay where you left it when filtering your Pivot Table it would stay there making it seem like you have not data.