Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content

Inserting QVS files in load scripts

You can insert QVS files into load scripts in Data load editor and Script.

You insert QVS files into your load script from Data sources in your script editor. Inserting the script adds the system variable Must_Include with the definition of the path to the QVS file. For example, $(Must_Include=lib://DataFiles/test.qvs). You can also manually define your own QVS files to include in the load script using Must_Include. For more information on Must_Include, see Include.

Viewing inserted QVS files

Under Included scripts, you can view QVS files you have inserted that have been successfully included during the last run of Preview data, Load data, or Export data. You can select a QVS file to preview the inserted load script.

Included scripts in Script

Script editor showing a QVS script selected in Included scripts.

In the load script, you can click </> after an inserted script to view a preview of the inserted script.

Preview of an inserted QVS script in Script

Preview of an inserted QVS script in Script editor. The preview shows the QVS script with an option to Open the script.

Inserting QVS from Data sources

  1. In Data sources, do one of the following:

    • For uploaded QVS files, under DataFiles, click Select script.

    • For QVS files in web storage, under the corresponding web storage connection, click Select script.

  2. Select the script and click Next.

  3. Click Insert script.

Limitations

Inserting scripts have the following limitations:

  • In Qlik Sense Desktop, Select script only supports references to native file connections. References to files in cloud-based storage providers, such as Amazon S3 or Dropbox, are not supported.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!