The ONLY way I am able to get this working is by:
1. Putting the batch file in a local folder on the Qlik Sense Server.
2. Then create a library path for that folder location in the Qlik Sense App
3. Hardcode the folder location in the batch file. Like this
Move /y "\\Testing\F1\*.*" "\\Testing\F2\"
4. Execute the batch file using that library path. Like this:
Execute [lib://ASTesting/Move2.bat] ;
I think i'm having similar behaviour with a script that was previosuly working fine, but now does not with our QS Nov installation.
In my example i'm automating the ForFiles command, when i run my command from inside QS this does nothing, but when i use the exact same command directly into a cmd prompt, it works fine.
The required settings.ini and QS Engine settings are in place to enable 'legacy mode'. Strange that only certain commands are affected, others still run with the Execute command as expected.