In our dashboard we used the binary load statement, followed by an app id. A couple of days ago we've upgraded our qlik sense environment and this isn't working anymore. We need to use the appname, followed by extension qvf..
However, I can't find those "named" qvf files on our server. We only have the files with an AppId as identifier.
For sake of completeness, I've added the things I've tried so far:
I'm running an app from my work environment
There's an app in a stream, called Klantmonitor, so no special characters involved.
I can't find a file on server named Klantmonitor.qvf, I do see a file with the app id in folder d:\qlikshare\apps.
I tried:
Binary Klantmonitor.qvf; Results in: No qualified path for file: ***
Binary [lib://Qlik Sense Apps (binary load source)/Klantmonitor.qvf]; Results in: Filesize for D:\\Qlikshare\Apps\Klantmonitor.qvf failed: The system cannot find the file specified.
Binary D:\\Qlikshare\Apps\Klantmonitor.qvf; Results in: This statement only works with lib:// paths in this script mode.
Binary [076d5faf-3e50-47da-9cc1-7c7a1a55db39]; Results in: No qualified path for file: ***
Correct. This is in the documentation as well, and has been for at least a couple of years, though I guess perhaps it previously worked contrary to documentation.
You cannot use binary to load data from an app on the same Qlik Sense Enterprise deployment by referring to the app ID. You can only load from a .qvf file.
Hmm... I interpreted the documentation in the wrong way. Apparently the import of a qvf as a binary can only be done now when placed manually somewhere on the server. That is something which is not gonna work for us.
Off course we do have the option of automating this with the commandline option, but in this specific case we have found another way.
Thanks for contributing and thinking about this problem with me!
