Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We recently upgraded from QlikView April 2019 to May 2021. Upgrade went smoothly and all QVWs run correctly - but only on Internet Explorer.
If we open a QVW through the Access point on either Chrome or Edge, the screen tends to freeze after a few data selections. If I select a few filters then maximize a chart, the app will not allow me to change any data selection. Nor can I click buttons, change charts, minimize the open chart, or do anything else except refresh the screen. Which puts me back to the beginning with nothing open or selected.
This behaviour does not happen using Internet Explorer with the IE Plugin - only if we use Chrome or Edge.
If this can be fixed by a setting, please let me know. This was not an issue in the older version of QlikView.
Hi @johnmart61 , can you please clarify "However, after the Excel spreadsheet has been read, saved, closed or whatever, the user is unable to return to the QlikView application."?
Is the Excel spreadsheet been worked on in a locally-installed Excel client, or within the browser (like in an online version of Office or Google Sheets)? Any chance that you could link a video or animated gif documenting the process and what goes wrong? Thanks!
Excel is local. QlikView is on the Web - in Chrome.
This problem has been going on since we upgraded to version 12.6.
Installing 12.6 SR2 helped but not completely.
I found yesterday that some of the export problem was caused when a QlikView tab had an On Leave Sheet trigger setting a variable. I removed all of those but the problem still occurs in some cases.
I am posting a video of the issue.
Hi, just for information, have you managed to find a solution to this problem since last time ?
Hello @johnmart61 ,
Thanks for posting.
I know there was an issue when moving columns on tables that could lead to the app freezing and this will be fixed in the next May 2022 that will be out shortly. So you might want to test the new version when is out to check if it resolves the remaining issues you have mentioned.
Cheers,
Albert
We have the same issue as @johnmart61 with some, but not all, of the QlikView applications. It doesn't matter if the user is using a deeplink or opens from AccessPoint. Excel export is not related in our cases.
When this is happening during a selection the java script console of edge throws this error:
Uncaught Error: cannot call methods on combobox prior to initialization; attempted to call method 'option'
QvAjax.js:353
Uncaught Error: cannot call methods on combobox prior to initialization; attempted to call method 'option'
at Function.error (QvAjax.js:353:225)
at HTMLTableCellElement.<anonymous> (QvAjax.js:515:63)
at Function.each (QvAjax.js:354:97)
at r.fn.init.each (QvAjax.js:351:85)
at r.fn.init.e.fn.<computed> [as combobox] (QvAjax.js:514:498)
at Qva.Mgr.bookmarksselect.Paint2 (QvAjax.js:1383:308)
at Qva.Mgr.bookmarksselect.Paint (QvAjax.js:1384:21)
at Qva.PageBinding.UpdateBookMarks (QvAjax.js:1012:273)
at Qva.Mgr.bookmarks.Paint (QvAjax.js:1388:325)
at Qva.PageBinding.PaintTree (QvAjax.js:1075:337)
at Qva.PageBinding.PaintTree (QvAjax.js:1076:10)
at Qva.PageBinding.Ready (QvAjax.js:1067:311)
at Qva.PageBinding.Ready (QvAjax.js:1070:454)
at XMLHttpRequest.f.onreadystatechange (QvAjax.js:1181:3)
The issue does occur once per application per session here. That means if you hit F5 after the first error it works from then on.
Maybe that helps investigating the fix?
@Albert_Candelario Do you have already an updated ETA for the version with the fix?
@schlettig Qv12.70.20000 is currently available on our download page https://community.qlik.com/t5/Downloads/tkb-p/Downloads
Hello @schlettig ,
Kindly test 12.70 IR and let us know if it resolves your issue. If not maybe would be better to post a new discussion as it might be a different topic.
Cheers,
Albert
thanks @Jill_Masinde and @Albert_Candelario ,
i was hoping on an ETA for a patch release for 12.6. Is there anything to be expected this year?
(As 12.7 IR is a new version, we cannot install or test it easily.)
@schlettig is the issue something you could reproduce in QV Desktop? If yes, it will be good to test QV Desktop version 12.70 IR as it will be much easier than test a full server and this way you can ensure your issue is also fixed as it might be a different one as mentioned above.
Cheers,
Albert