Skip to main content
Announcements
Introducing a new Enhanced File Management feature in Qlik Cloud! GET THE DETAILS!
cancel
Showing results for 
Search instead for 
Did you mean: 
cotiso_hanganu
Partner - Creator III
Partner - Creator III

Unstable behaviour of EXECUTE in qliksense script to reload qlikview apps

Trying to launch an QV reload from the script of a QlikSense Desktop App.

In principle this requires combining

  • licensed Qlik Sense Desktop (free/from SaaS Server/from on Win Server)
  • licensed Qlikview Desktop
  • QS app with an EXECUTE comand, like
    EXECUTE cmd.exe /c "<FullPathOfQlikView>\QV.exe" -r "<FullPath>\MyApp.QVW" 
  • QVW MyApp

This is not actually working for some security  reasons (I would call them misunderstandings between windows and qlik),
so we need an extra BAT file that contains the reload prompt command:
"<FullPathOfQlikView>\QV.exe" -r "<FullPath>\MyApp.QVW" 
while the EXECUTE in QS app script should just pointing to the BAT:
EXECUTE cmd.exe /c "<FullPathOfBatFile>\MyBATfile.BAT" 

Of course some things have to be considered, in order to make it all work:

  • Qlik Sense Desktop should be running in legacy mode 
  • Qlikview should have some security settings applied in order to be able to run the reload in prompt command

Strange enough, all these are some times working, some times not working, without really understanding this instability.

Any suggestions ? 

 

Labels (1)
2 Replies
cotiso_hanganu
Partner - Creator III
Partner - Creator III
Author

  • Latest findings:
    created a BAT that calls 2 reloads, of 2 QVW files, one located on C: and one one d:
  • copied the BAT both on C: & d: 
  • launched the 2 instances of the BAT from win explorer (both)
    =>  both reloads within each BAT run successfully
  • called the 2 instances of the BAT with EXECUTE from  Qlik Sense Desktop
    =>  only BAT on C run successfully

Can anyone confirm ?

Do you believe it's a bug ?

marcus_sommer

C: is probably a "real" path while 😧 might be not a local partition on a local disk else any kind of a mapped drive which may not be existing and/or accessible at time of the call and/ore responding in time. Also the syntax could have an impact because unc-paths are not always supported.