Qlik Community

Qlik Sense Integration, Extensions, & APIs

Discussion board where members can learn more about Integration, Extensions and API’s for Qlik Sense.

Announcements
Qlik® Product Spotlight: Discover what’s possible. Get more from our products.
See for yourself. Register today.
agottwald
New Contributor

Internet connection regression in 2.2.3

Hello,

With the latest 2.2.3 release we've noticed a massive regression with Webfile connections

We're loading large amounts of generated data from a service into QlikSense. The connection is dynamicly created with CreateConnection and ModifyConnection. Those requests are taking much longer after the upgrade to 2.2.3.

Version 2.1.1 (tested with Qlik Sense Desktop 2.1.1+Build 22) read only a small part of the data when it tested the existence of the URL on CreateConnection or ModifyConnection. Version 2.2.3 (Qlik Sense Desktop 2.2.3+Build:37) reads the complete data.

This can be observed in the Qlik Sense Desktop Hub when creating a webfile connection.

The same thing happens in the data preview dialog. 2.1 read only 100 lines while 2.2 reads the complete data.

We've been able to monitor this behaviour in our service logs too.

2.1 reads only a small portion. The export is aborted once the web connection is closed and only a few lines are exported:

INFO: Export finished:15 data rows exported

INFO: Export finished:1097 data rows exported

INFO: Export finished:108 data rows exported

INFO: Export finished:243 data rows exported

2.2 reads the complete data. The export processes all 576916 records of generated data

INFO: Export finished:576916 data rows exported

INFO: Export finished:576916 data rows exported

INFO: Export finished:576916 data rows exported

Is there a possible workaround to instruct the connection to only load a small portion of the data when checking the existence or loading the preview?

1 Reply
agottwald
New Contributor

Re: Internet connection regression in 2.2.3

According to Qlik Support this has been recognized as a bug and will be fixed in Qlik Sense 3.0