Disable Data Preview in Data Load Editor in Qlik Sense on Windows

[Vegar]

Is it possible to per default disable the data preview when opening the script editor on a Qlik Sense on Windows installation?

When a developer navigates to the Data Load Editor of an Qlik Sense application then the default view is to see script section to the left, the data connections to the right and the data preview tables in the bottom. Populating these views, sometimes  makes the data editor page use substantial amount of time to fully render it self so it is possible for the developer to do script changes or initiate a reload.

We handle some very large applications and we believe being able to disable the data preview in the load script editor would speed up the rendering of the load script editor page. 

I have not found any documentation on how to set the default state to disable disable the preview. Is it possible to configure Qlik Sense to do this, either on environmental or by app level. 

(The environment is running Qlik Sense November 2024 on multiple nodes)

[Chanty4u]

To be honest there is no official setting 

But you can raise a feature request with Qlik Support to request an option to disable data preview by default.

[Or]

I agree that this is annoying and I also don't know any way around it built into the product. Since it seems to preview the first table in your load script (at least most of the time), you can create a dummy island table at the top of your script e.g.

FIRST:
Load 'Hello' as World Autogenerate(1);

And then the preview would just show that, which isn't time consuming. Kinda stupid and clunky, but better than waiting excessive amounts of time any time you open the script, probably?

[Vegar]

@Chanty4u I was hoping that someone knew a official (or non-official) setting to configure in order to fix this. This could could be a candidate for adding as a suggestion to the ideation section. 

@Or If your finding, that it is the first table in the script that gets populated, and that the time to render decreases by having a small table, then the "dummy" island or i island with some additional info about the app could be a decent workaround. 

[Or]

I wasn't very thorough about testing this, but it seemed to be the case on Cloud (I can't test Enterprise as the version I have access to predates the new layout). Near as I could tell, it will populate the first table when first opened, and then whichever one you left it on after. Of course, once you've opened Data Load Editor the first time, you can just collapse the section and not worry about it until you time out...

[Digvijay_Singh]

Its our first day on Nov 2024, I think following your experience, I would open a small app, switch the preview off and work on heavy stuff :), Hope Qlik will provide better way e.g. a setting in the app to enable/disable it.

[Or]

Again, I was not thorough in my testing, but it might remember the pane's status per app, rather than globally. Something worth testing though. I've only looked at it in Cloud and only in passing since my Cloud tenant is just the MVP one, I don't actively use it much.

[Vegar]

I did some sample testing, changing the first table from a the large transaction table to a smaller island table, on a couple of our larger applications. 

It seems to work as you suggested @Or , but I don't see any improvement in rendering time. I get the impression that the rendering time is independent from which table that gets rendered in the preview. 

I have not solved my issue, but I made a small learning 💡 on how the table script order affecting the selected table to preview per default.

Thank you for your inputs on this @Chanty4u @Or and @Digvijay_Singh 

[Or]

Odd. There was definitely a difference for me - I whipped up a quick script to make a stupidly large table (2000 rows by 2000 columns) and it took a fair while to preview, and I got faster previews when I put a small table in front of it.

Perhaps @Digvijay_Singh 's suggestion will work? Worth testing, anyway.

[Digvijay_Singh]

I have been testing in On-Premise platform after upgrading to Nov 2024 last weekend.

Its really very confusing when do we see 'Preview' button enabled or disabled. Today morning atfer connecting to our office VPN, the very first app I opened didn't have 'Preview' enabled. Did that keep my status of last click on that button, not sure!!

I think so far I agree with @Vegar , rendering time is independent from which table that gets rendered in the preview. Our first table is always a release note table with normally a less than 8-10 rows but it takes a lot of time to open even that table in preview when I have 'Preview' enabled.

Thanks,