Skip to main content
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. READ MORE

QlikView 11.20 End of Support Upgrade: Known Issues and changes in product behavior

No ratings
Showing results for 
Search instead for 
Did you mean: 
Digital Support
Digital Support

QlikView 11.20 End of Support Upgrade: Known Issues and changes in product behavior

Last Update:

Mar 24, 2022 8:09:41 AM

Updated By:


Created date:

Mar 12, 2018 11:46:29 AM

Known issues experienced when performing an upgrade of QlikView 11.20 to any of the later versions.

Applies for an upgrade to:
QlikView 12.20 / November 2017 What's New in QlikView November 2017
QlikView 12.30 / November 2018 What's New in QlikView November 2018
QlikView 12.40 / April 2019 What's New in QlikView April 2019
QlikView 12.50 / April 2020 What's New in QlikView April 2020
QlikView 12.60 / May 2021 What's New in QlikView May 2021

The linked information is not exclusive to problems, but also includes changes in behavior. 

Preparation for an Upgrade

Review the Upgrade Instructions as documented on our official Online Help.

Watch our Upgrading from QlikView 11.20 recording, which covers the end of support for QlikView 11.20 including:

  • What to consider before upgrading 
  • What to expect after upgrading to QlikView 12.10 or QlikView November 2017 or beyond
  • Major architectural differences introduced in 12.10 and November 2017 or beyond
  • How they will change the behavior of your QlikView deployment for the better 
  • New features available after upgrading


Intended Changes


User / Administrator impact behavior change

Tasks are not executed as expected and are shown in status Queued
Tasks that may have originally failed due to resource constraints, or destabilized the QlikView environment, will now be queued.  A queueing system was introduced in QlikView 12.10, which works together with an overload protection to help stabilize the QlikView environment.  This change is part of the improved Publisher load balancing introduced in version 12.10.  
Unable To Export Large Objects To Excel After Upgrading to November 2017
To prevent large exports from causing system instability, time and memory limits have been implemented, and this can result in exports failing or delivering only partial data.  These limits can be changed to accommodate larger exports.  
Reloads that were functioning fine in QlikView 11.20 or QlikView 12.x, begin to fail after an upgrade to QlikView November 2017. Reload tasks that completed successfully in QlikView 11.2 or 12.x may fail after an upgrade to the November 2017 release.
A new script reload mode was introduced in the November 2017 release, and this can result in some scripts failing.  Reloads now use the BNF mode.  This change adds consistency to the product, as reloads now use the same syntax checks as the script editor.  For details about the change and guidance on avoiding errors resulting from this change, see QlikView November 2017: Failing reloads and BNF script reload mode.    
Send to Excel feature now uses the .xlsx format by default beginning in the November 2017 release. In earlier versions, the default format was .xls.  QlikView now uses the same default file format as Microsoft.  The change to .xlsx improves exporting performance and stability.
QlikView 12 Task - Log files are copied at the successful end of a reload and do not appear in the standard location when a reload is in process.  Beginning in QlikView 12 SR1, document reload logs are written locally on the node handling the task and stored in %ProgramData%\QlikTech\ QlikViewBatch. 
When the reload completes, the log is then copied to the Source Document folder and the QDS Application Data folder.  This change is a log optimization for QlikView Publisher.  It was implemented to avoid the increase in reload times that can occur when logs are written to remote folders during the reload. For details, see the QlikView 12 SR1 release notes.  
Before() function does not calculate properly if “Suppress Zero-Values” is checked in the Chart Properties > Presentation tab. Beginning in QlikView 12, the suppress zero setting is now fully applied in conjunction with inter-record functions, but this was not the case in earlier versions. See Internal behavior change of before() function in Qlikview 12 and later.
Change in how alternate states evaulate and expand variables Beginning in QlikView 12, variables always belong to a specific alternate state, eliminating the random behavior that could occur with alternate states in earlier versions of QlikView.  After an upgrade, QlikView documents using more than one alternate state should be tested to verify that alternate state still renders the desired outcome.  
The sort order in a table is not correct after the upgrade to QlikView 12.10
Sort order for charts containing disabled/hidden columns is set to default after the upgrade.  This is a result of changes made to resolve inconsistent sorting behavior in charts containing disabled/hidden columns. 
Functions that refer to paths fail, while they used to work in 11.20
Functions are failing because of changes in how relative paths are handled. In QlikView versions 12 and later, functions have been improved to reference paths relative to the Directory statement, rather than to the location of the .qvw, as in earlier versions.  
Quotes in Set Analysis change in behavior - "error in expression" or "incomplete visualization" or "... These errors are often the result of an incorrect use of single and double quotation marks.  The errors did not occur in earlier versions because a defect prevented QlikView from recognizing the differences between single and double quotes.  The product defect has been fixed, and single and double quotes must now be used correctly.  For details, see the following resources:
After upgrading, opening or navigating in a document results in “Lost Connection to Server, Reconnecting” messages.

Time-out settings are now applied using SocketTimeOutInSeconds in the WebServer settings.  These settings override the QVSTimeout setting that was used in previous versions of QlikView.  This change was made to add consistency in timeout settings between services. See QVStimeout Overridden by new WebServer Setting for details. 

Reloading a script in QlikView 12 fails with "ApplyMap error: map_id not found"
In versions 12.10 SR6 and later, a mapping table must be loaded before the ApplyMap() function can run. Unless a mapping table has been loaded, scripts that reloaded successfully in earlier versions will now fail to reload with the following error: “ApplyMap error: map_id not found.” 
Pie charts behave differently in versions 12.10 and higher. When dimension limits are applied and total grouping mode was added to the expression, the order of the dimensions was reversed in 11.2 and 12.0.  The order is no longer reversed in versions 12.10 and later.  The behavior in versions 11.2 and 12.0 was the result of a product defect that was fixed in 12.10.  
Calendar objects no longer close or minimize after a selection is made
In version 11.2, the calendar object closes when a selection is made.  To close the object in versions 12.x and higher, you must now click outside the calendar area.  This is a design change relating to the touch enhancements implemented in QlikView 12.  



Issues encountered


User / Administrator impact  

QlikView 12: dashboard stuck on Loading in Internet Explorer - Qva is undefined

QlikView 12 removes support for IE 8, 9, and 10.  Compatiblity modes and old browser versions lead to the Full Browser (ajax) Client to no longer work. 
Issue with "XPassword" and OLE DB SQL Server Native Client 11.0 Driver in QlikView November 2017 (12... Issues connecting to the OLE DB SQL Server Native Client Driver due to Integrated Security.
Labels (2)
Partner - Creator
Partner - Creator

what are the issues and bugs encountered in 12.5 version?

Digital Support
Digital Support

Hello @kumarbala For known issues in new releases, I'd recommend reviewing the Release Notes for the version you would like to investigate as known issues are regularly updated in them. They can be found on our download page.


@kumarbala Send to Excel feature now uses the .xlsx format by default beginning in the November 2017 release.

Version history
Last update:
‎2022-03-24 08:09 AM
Updated by: