topic Re: Binary load with app ID is not working in May 2025 in App Development

Binary load with app ID is not working in May 2025

Tool_Tip — Thu, 11 Sep 2025 06:22:05 GMT

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?

Re: Binary load with app ID is not working in May 2025

Lech_Miszkiewicz — Thu, 11 Sep 2025 06:48:56 GMT

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

Re: Binary load with app ID is not working in May 2025

Tool_Tip — Thu, 11 Sep 2025 07:03:59 GMT

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?

Re: Binary load with app ID is not working in May 2025

Lech_Miszkiewicz — Thu, 11 Sep 2025 07:44:21 GMT

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-when-using-app/ta-p/1713804 where Qlik personel was invovled.

cheers

Re: Binary load with app ID is not working in May 2025

Tool_Tip — Thu, 11 Sep 2025 08:38:17 GMT

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?

Re: Binary load with app ID is not working in May 2025

Lech_Miszkiewicz — Thu, 11 Sep 2025 10:14:21 GMT

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

Re: Binary load with app ID is not working in May 2025

Or — Thu, 11 Sep 2025 10:34:43 GMT

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.

Re: Binary load with app ID is not working in May 2025

Tool_Tip — Thu, 11 Sep 2025 11:34:00 GMT

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 ?

Re: Binary load with app ID is not working in May 2025

Lech_Miszkiewicz — Thu, 11 Sep 2025 12:21:29 GMT

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

Re: Binary load with app ID is not working in May 2025

Or — Thu, 11 Sep 2025 12:29:41 GMT

@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/ScriptRegularStatements/Binary.htm

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\

Re: Binary load with app ID is not working in May 2025

Lech_Miszkiewicz — Thu, 11 Sep 2025 12:41:18 GMT

Hi @Or

that is not the issue here. What you have shown misses the main point of the root cause of the issue which is that binary load now only supports load from .qvf and .qvw files only.

So the whole recent change is that by default apps are stored as QVF files but without actual .qvf extension in shared path\Apps folder which in the past was still allowed to be binary loaded and now isn't unless you include the EnableQvfPathValidation=0 in the settings.ini.

cheers

Re: Binary load with app ID is not working in May 2025

Or — Thu, 11 Sep 2025 12:56:59 GMT

@Lech_Miszkiewicz Fair enough - the original post described the issue as being unable to access apps via ID, to which I replied with the documentation quote that this is not supported (and suggested the syntax spelled out by the documentation as an alternative). Seems like what you're describing should probably be part of the documentation, but I have no idea who at Qlik I should tag for that...

Re: Binary load with app ID is not working in May 2025

Lech_Miszkiewicz — Thu, 11 Sep 2025 13:18:40 GMT

No worries @Or . You may want to go through the comments we put here and links to other posts as they explain all the binary issues and reasons.

In Qlik Sense Enterprise on Windows you would have folder connection pointing to your \\server\share\apps location in which you would have files with names the same as app ID’s. Thats whats this post refers to.

So then in your Qlik sense script you would have statement like:

Lib://AppsFolder/5dhdjdh-6389-4653gh-dkyy

note that 5dhdjdh-6389-4653gh-dkyy does not have .qvf extensions as those files are not having extensions.

With that change Qlik prevents load from files without extension (unless you do .ini change) making it actually difficult to use binary load statement.
Documentation is ok as Qlik is not really recommending binary load directly from the apps. Instead Qliks suggestion is to copy app files using 3rd party tools or even just windows command and during that process adding .qvf extensions to them to then allow for binary load from copied files with extension. To me it is not viable solution so we go with change to settings file.

hope that clarifies it.

i dont think we need to tag anyone at qlik. This topic is covered by support guys in the link i provided in other comments

cheers

Re: Binary load with app ID is not working in May 2025

Kaushik2020 — Thu, 22 Jan 2026 15:03:28 GMT

I Tried creating a path with Name APPS_New with the path same in Server cluster and it worked.

Re: Binary load with app ID is not working in May 2025

Lech_Miszkiewicz — Thu, 22 Jan 2026 22:08:30 GMT

Hi @Kaushik2020

your one liner is little bit vague. What worked? Creating path will work, but binary load from it will not unless you have older version of Qlik Sense which still supports binary load without .qvf/,qvw extension or have settings.ini changed as I mentioned earlier. You may want to check all requirements for binary load and give us clearer perspective what has worked for you with the examples of the steps you have taken?

You may not even be aware that settings.ini has been changed by someone and then everything looks like it used to before.

cheers