Binary load with app ID is not working in May 2025

[Tool_Tip]

Dear experts

We have upgraded Qliksense from Nov 2025 to May 2025 patch 5 and we found that none of our application is working with binary load with app ID.

Is this new issue or is there any relative solution?

[Lech_Miszkiewicz]

HI @Tool_Tip 

Have you applied change to the settings.ini? The responsible part for this would be:EnableQvfPathValidation=0 

Below are my legacy and current settings from: C:\ProgramData\Qlik\Sense\Engine settings.ini file

[Settings 7]
OverrideScriptSecurity=1
EnableRefMasterMeasure=1
EnableQvfPathValidation=0

Binary was deemed risky by Qlik and security was harden (not from cyber attack perspective but rather from data exploitation point of view by "smart people who would have known how to use binary to load data they should not have access to in some instances).

cheers 

[Tool_Tip]

Dear Leck

I’m confident that the suggested solution will work, as I’ve seen clients confirm it on the community. However, I’d like to verify if this solution is permanent and officially confirmed by Qlik.

Can we proceed with applying it in the production environment?

[Lech_Miszkiewicz]

Hi, 

The actual solution suggested by Qlik is not to use binary load at all and use other solutions like storing data models to .qvd files and then loading data to other apps also from .qvd files or moving apps to other folders and appending .qvf extensions to them.

The setting on the engine allows you to override that and obviously it is there so you can apply it and still use binary load if you want to...so,

If you want to keep using binary load you just have to make sure you make this entry to settings.ini. There will be no other solution to that.

As far as I remember this was the discussion: https://community.qlik.com/t5/Official-Support-Articles/Binary-load-fails-with-General-Script-Error-... where Qlik personel was invovled.  

cheers

[Tool_Tip]

Thank you, Leck, for the detailed information. If we add the above entry to the settings.ini file, it should resolve the issue. However, will we need to reapply this change after every upgrade?

[Lech_Miszkiewicz]

That I don't know. I keep backup of the ini file each time I do upgrade so for me it is a no-brainer to make sure those (and some other config files) are still the same after upgrade.

I normally don't even bother checking it. It is just part of my routine and good practice while doing upgrade for a client. 

cheers

[Or]

According to the documentation:

This has been the case for quite a while, but it did still work (unofficially) until recently. You should consider switching to path/file references instead if you want to continue using binary load. 

[Tool_Tip]

Dear MVP,

switching to path/file references - Here do you mean to create data connection for each application ?
Let us know in detail how to switch to path/file reference ?

[Lech_Miszkiewicz]

Hey @Or , what do you mean?

Without implementing 3rd party solution (or without the ini setting i mentioned) you will not be able to do binary load. We had quite thorough discussion about this with other MVPs and Ambassadors when that change was released around Nov 2024 so can you explain what do you mean by use of  "path/file references"?

cheers

Lech

[Or]

@Lech_Miszkiewicz  @Tool_Tip 

Just spelling out the documentation - I have no information past that in this case, but note that this is the documentation for the most recent QS version at the moment. If your experience suggests otherwise, it may be that the official documentation is incorrect or that the versions in question have a bug that needs squashing. 

https://help.qlik.com/en-US/sense/May2025/Subsystems/Hub/Content/Sense_Hub/Scripting/ScriptRegularSt...

The path to the file which should be a reference to a folder data connection. This is required if the file is not located in the Qlik Sense working directory. Working directory Example: 'lib://Table Files/' In legacy scripting mode, the following path formats are also supported: absolute Example: c:\data\ relative to the app containing this script line. Example: data\