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

[CJ_Bauder]

Amazing addition that I suspect will serve as a great tool / partner to QVS files for source cont on script.

One question - is there any roadmap plans to enable/disable Intellisense auto prompt text in script? At times this can be very helpful, but sometimes the automatic injection hinders development.

Thanks!

[luizcdepaula]

@Michael_Tarallo  thanks for the post. Good feature. @mshann01 makes a great point, we need asap a true QMC with centralized capability to manage reloads and be able to run somebody else automation. If an automation fails, I need to transfer ownership before doing anything, and it doesn't help with collaboration. Hopefully that will come soon.

@StefanBackstrand I believe the use of app for the data model viewer still makes more sense, and then eventually transfer the final script to the script object. I like to use the report capability in a sheet still for validation and check dups and nulls after joining tables.

Cheers,

Luiz DP

[visualfacts]

@Michael_Tarallo this is a simple but great feature, love it. We extensively use this layered approach having apps to create qvds with analytics ready models. Consuming apps just load * from *.qvd and ready, voilà.

Two points:

- is there any chance to have that great function in the on-prem version?

- is there any chance to protect theses scripts (apps) from any reading or copying?

The second point is important for us. We are consultants and these scripts (apps) contain mathematical/statistical methods and data modelling techniqes that are our intellectual propterty. As our customers have admin rights we need something beyond the security rules (like in QV, hide script)

Thanks for your answer in advance!

[StefanBackstrand]

@luizcdepaula Can you elaborate what you mean with using "the report capability in a sheet still for validation and check dups and nulls after joining tables".

Are you talking about reports in QAA, Logical Model or something else I'm missing? Or are you talking about the meta data in the Data Model viewer?

[visualfacts]

@Michael_Tarallo Is there a way to "include" a script object just like the standard $(include ...) within an app and so use the same load script for different apps?

[Greg_Oliven]

This is such a great addition.

[Michael_Tarallo]

Hi guys - in regards to the the question asked by Visual - no not yet but it is on the roadmap I am told. Stay well all 🙂

[ester_pr]

Hi, everyone,
Is it possible to call the script from within an application?
For example a table that I run in several models, save and delete, each model that runs will go to the same script will run and continue to run in the internal script

Thanks

[Florentin74]

I am also looking very much forward to the "include" reference to the "script object". Today we are using qvs files a lot. Gives us the possibility to have the entire "data pipeline" within the actual end user app and still being able to use the same scripts across various apps.  

Regards,

Anders