Introducing a new Script object and Script Editor and more!

[Michael_Tarallo]

What if you could prepare data (join, transform, STORE, etc.) using Qlik script - WITHOUT creating a standalone app - without sheets? Would you like that? Well, would you? Well now you can - introducing our new script object and script editor - with data preview and more! Watch this #qlik #SaaSin60 to learn more!

We have now added the ability to create Qlik scripts directly from the hub, ana managed in the catalog -  using a new and improved script editor.  Users can now build and deploy Qlik scripts upstream of analytics apps, which can be executed and result in output files in formats such as QVD and PARQUET that can be stored in the hub and used for analytics and AutoML applications.  The script editor also now includes a data preview feature, allowing users to get better insight when developing scripts.  This provides our customers with an improved workflow for preparing data, while setting the stage for future enhancements to analytics data prep capabilities.

• Watch More in 60: 
• Can't see the video? YouTube blocked by your region or organization?  Watch it here

[NickRondeel]

Great feature! Also nice that we can convert a "analytic app"  back to a "script only" app. (and vice versa) 

[juraj_misina]

This is very nice. Can we also use these script objects in other apps in include/must_include fashion? That would be extremly useful when creating a repository of common scripts and sub routines within a tenant.

[PrashantSangle]

interesting ..🤔  Thinking about use case 

I think If we are able to load script file in app then it is more useful in terms of script security.

[mshann01]

A nice feature for sure but not nearly as important as the backlog of more significant missing features.  How do we not yet have a QMC that is at least half as capable as the on-prem version?

[Or]

@Michael_Tarallo Like @PrashantSangle , I'm trying to understand the use cases for this. Any chance of a follow-up explaining how this is better than just using an app?

[Michael_Tarallo]

Hi Guys - thanks for your comments / question - I will try to summarize.

currently - you cannot reference "Scripts" in the same way as you cant reference "apps",  (like if you were to perform a binary load etc. -  but you can include a "qvs". We have the script/app include on the roadmap.

In regards to use cases, this is going to greatly depend on your existing knowledge of how Qlik does things with Qlik script. If you are new to Qlik - you might ask why do I even need this? In many assistances you may not. 

To summarize - you would use a script object to perform additional data operations such as joining or transforming data. Sometimes your data source is not exactly in the format you need for analytics and you can use powerful Qlik script to transform it. for example I have a script object that exports data from a RESTful service, cleans it up, creates new fields and uses the STORE command to write it to a QVD file that I then use for analytics. I don't need to create a standalone analytics app for it and now I also have an individual object I can manage in the catalog and eventually reference as a single object from other apps and scripts.

If you need further clarification please let me know

[StefanBackstrand]

@Michael_Tarallo Thanks for the response. My first thought was "How do I include this script?", so I'm glad it's on the roadmap. Being able to build scripts that are managed, developed and source controlled this way, natively in Qlik, and include them in each other - allowing structured re-use and dependencies - would an absolute game changer for any Qlik developer.

[barnabyd]

Thanks @Michael_Tarallo for the update. My clients are still almost entirely on prem, so my cloud experience is still minimal. However, a couple of things stood out to me as important improvements. First, the data preview is a feature that we have not had in any version of Qlik before and it is one of the few features where Power BI has been better than Qlik - so this is a brilliant addition! Second, when I build an extract or transformation app to store to QVD, I always add a data summary sheet to list the tables that were loaded, how many rows for each one and how long the load took - so it seems I won't need to do that in the cloud now.

Cheers, Barnaby.

P.S. I also agree with @mshann01 that there are other features that I would have thought were more important. Qlik Cloud is missing important features that are in QS on prem, which is missing important features that we had in QlikView. Yes, I'm still hoping for some of my favourite QlikView features to come back!

[paulcalvet]

Hello,

I think this feature is good. For exemple, I love the fact that I can quickly see data uploaded and the qvds generated by the application. It could be usefull when application use QVDs for self service.

I also try to insert this new object in an automation and it's the same object that a standard application, so it minimize the modification in task chain automation.

To follow the conversation, the cloud is really top, I wouldn't go back to on premise for anything, automation, update all weeks, etc. we've really cut back on administration compared with on-premise, to focus on delivering quality applications faster

For me, the only really negative point I find with the cloud version is the absence of a detailed log on application consumption, so you don't know who's doing what (who's really using sheet creation, for example).

And please update also the 5GB applications (also for classic license), it's really not much, even with ultra-optimized applications.

Thanks,

[Kunal12164]

@Michael_Tarallo if we store a file in qvd or csv format then how we can download that file or we can store that file in google drive. please give a solution on this. thanks in advance.