On Qlik Sense for Windows release May 2026 - Published apps don't show the optio "Load Script Editor"
Hi to everyone,
After upgrading Qlik Sense for Windows to the release May 2026 Patch 3, when I try to open the Load Script for any published app, I can't. The option "Load Script Editor" is missing. This option was present for the release Nov 2025 Patch 6.
I tried to create new rules to permit it with no luck.
I know, that the way can be to duplicate the app, and see the script, but I would like to know if this behaviour was set by design, and any workaround can't be set via security rules, or so on, or if it's possible.
Was anyone able to set the behaviour I'm missing? if so, can you explain me how to set it?
We are experiencing the same issue after upgrading to QSEoW May 2026 Patch 3. Before upgrading, security rules permitted load script editing for published apps. After upgrade we are unable to open Data Load Editor for published apps. All the same security rules are still in place without alterations. I confirmed this by comparing the postgres db backup taken before upgrade to a copy after upgrade (systemrules.sql).
I created a ticket for support. Their response was that this is an engine-level regression.
not at this time. I hope Qlik will mark this down as a bug and come with a solution.
I suspect this is the result for reacting to a bug reported earlier. After initial release, users were able to edit the load script for published apps by mistake. See link to the bug and description.
Hi @rzenere_avvale , not yet. A collegue of mine is working on the issue in @ollis case. Please, log a support case mentioning this discussion, so that we can have more weight on the problem. Thanks!
Daniele - Principal Technical Support Engineer & SaaS Support Coordinator at Qlik If a post helps to resolve your issue, please accept it as a Solution.
Editing the load script directly on a published app is not possible by design in QSEoW.
Oh man! I don't know if it was set by design but it was working perfectly for me for the last seven years. I'm wondering when a bug becomes into a useful feature.
Having briefly enabled this option by accident with a custom security rule many years ago, I absolutely hated the fact that this was an option in the first place. The ability to read script would be great, but to change, not so mcuh. I didn't report it, assuming this was intentional behavior since it required a custom security rule.
That said, one man's bug is another man's feature.
If you're just looking to read the script without having to duplicate, it's fairly easy to just grab all the scripts for published apps via API on a scheduled basis. That's what I ended up doing.
Let's say that to change anything, the right way is to duplicate the app, modidy and test it. If the result is fine, then it's time to republish it. In my humble opinion, there's no discussion about the steps to follow if we don't want to break the solution. Furthermore when there's a task loading the app every x time.
However, when you just want to see something in your code, the possibility to see the Load Script is very helpful. I know that we can export the script via API, in my case I'm already doing it to synchronise it with GitLab, however the UX it's not exactly the same in Qlik than in GitLab or any other text editor. At the end, it seems that we have to change our mindset and adapt to the new way. I say new way because for a long period of time we have lived with this "bug", and a lot of people, like me, learnt to use it with care.
Not disagreeing at all. I think the ability to *see* the script should be default for people with certain permission levels.Unfortunately, Qlik seemingly didn't author it that way. They did originally allow for published-app editing - seemingly in error - but that's not at all the same thing. Unfortunately, it seems that post-update, all we have is workarounds.
