Vizlib Finance Changelog

Possibility to add comments on lower level cells. You can insert comments on lower level cells. Before, you could comment only top level cells. The feature applies to Vizlib Finance version 4.5.0. and higher. For more information on comments in Vizlib Finance, see Vizlib Finance Report Properties - Comments

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 Finance Report.

When the users took a snapshot of the Finance Report table and dragged it to the Storytelling sheet, columns or rows of the table were missing.

Important Announcement

Vizlib Finance v4.3.2 had a fix amended to it, which resulted in the column dimension title being processed in the intended way. However, this resulted in breaking changes for some users who relied on the old working method. We request that you please upgrade to the latest version of Vizlib Finance to resolve issues quickly whilst following the documentation listed in the changelog for Vizlib Finance Report v4.3.3.

For more information refer to the topic Add tags to the extension to fix incorrect dimension names under Limitations.

Incorrect Dimension name displayed in v4.3.1. Using the functions argb and rgba is not working as expected since the colors are incorrect.

Problem with calculation conditions in Qlik Cloud. For users switching through dimensions by using variables to turn dimensions and off, there was an issue where the top dimension would not display all the data columns.

Incorrect Dimension name displayed in v4.3.1.

A legacy feature or bug has been identified in versions 4.3.1 and lower, displaying the top dimension name based on the first dimension in the Dimension group within the Property panel. This issue happens when you have invalid calculation conditions (that is, the Calc. condition is not met; therefore, display = false).

Add tags to the extension to fix incorrect dimension names under Limitations.

Problem with calculation conditions in Qlik Cloud. A difference was spotted on how the Finance Report presented when using the Calculation condition. The result was that the column heading was still visible, but the numbers were hidden. This results in miss alignment between the numbers and the headings.

Allow values to be blank/empty on blank rows using a setting. A while back we fixed a bug that displayed values on empty rows. As it turns out, this bug was used by some customers to have blank values on rows. We added a simple checkbox setting in the property panel that allows you to "Hide values on blank rows". This reverts the behavior to not displaying anything on blank rows. (It is by default disabled to avoid breaking existing solutions so it needs to be turned on for this feature to be in effect.)

Comments disappear when they should not. Some rules of when to show comments was too strictly implemented and was hiding comments that should be shown.

Comments indicators are not visible until we make a selection. The small indicator icon would sometimes not show up until the user made a selection in the application.

Improve handling of line feed in exported text. With this release it is possible to export multi-line text in the additional info. Enable the setting in the property panel for multiple lines to be used. Note how the Qlik feature "getcurrentselections()" automatically ends up nicely on two rows.

Important: This feature is not available in scheduled reports until the next version of Vizlib Server. We recommend waiting with this update until the corresponding Vizlib Server is released.

Finance Report- dynamic title is not reflected on the exported file name. The exported title will now be correct even if it was based on an expression and selections changed it.

Important: This version requires an updated version of the Vizlib Server (v4.12.1)

Security update:

Follow the link below for the latest important security updates for Vizlib Extensions.

More information...

Vizlib Finance Online 4.0.0 and 4.1.1. Comments fail to work and initialize (Qlik SaaS).

Finance Comments now work with Qlik Cloud!

Important: This version of Finance Report requires version 4.11.0 (or higher) of Vizlib Server in order to work with comments!

Performance improvement - Finance Report does unnecessary calculations. An additional calculation of the table was done during filter selections leading to considerable performance degradation in some cases.

Exporting to EXCEL gives error message due to indicators. When using advanced mode for indicators Finance Report would throw an error message. Export of indicators and data- bars are not possible in advanced mode since Excel can not inherit the Qlik logic used in expressions but it should not lead to an error message. With this fix we also improved the documentation in the property panel to make limitations clear to the Qlik developers.

Important: When upgrading to this version of Finance Report, enterprise customers will also have to upgrade their Vizlib Server version to 4.11.0. Older versions are no longer supported.

Finance Comments on Qlik Cloud. Finance comments with Vizlib Server are now also available for Qlik SaaS customers! Enterprise grade commentary feature with plenty of configuration and security options.

A variable with this name already exists. Please choose another name error message. In some situations (typically when using more than one Finance Report on a sheet) this error message would show up. The problem was related to Viztips but could occur even when Viztips were not enabled.

Dimension dropdown Scroll Bar Missing in Qlik Sense versions later than Nov 2022.The issue occurred when using a longer list of alternative dimensions. A scrollbar should show up but in Feb 2023 version of Qlik Sense it did not.

Upgrading extension corrupted the measures. In later versions of Qlik Sense (tested Nov 2022) and in Qlik Cloud a measure could become corrupted and not show up in the visualization. It would still exist in the property panel.

Row measure values move when expanded. In some situations when expanding a dimension the measure values would "jump" one row.