Qlik Community

QlikView Documents

Documents for QlikView related information.

Announcements
QlikView Fans! We’d love to hear from you.
Share your QlikView feedback with the product team… Click here to participate in our 5-minute survey.
Rules, plus terms and conditions, can be found here.

Manage External Qlikview Scripts

Not applicable

Manage External Qlikview Scripts

Generally any scripting or programming languages will provide a option to import the same logic source code from other application or pre-existing utilities. In the same manner Qlikview scripting language provide a option to developers to import the external qlikview script files into qvw file. By using "Include" function in the script we can import any file have qlikview script code.

Ex: $(Include=\\servername\Global\GlobalEnvVariables.qvs);

This functionality is  more useful to change the DB connections if we deploy the qlikview application from Dev to QA or QA to Prod. Simply change the DB connection string on the scripts files so we don't need to do any script change while deploying from QA to Prod etc.

The one draw back is syntax checker didn't highlight any script error while validating. so developers needs to take care of correct syntax on the script files.

The other drawback is, if script file doesn't exist Qlikview script execution didn't throw an error. To avoid this we can use "Must_Include" function instead of "Include"

Ex: $(Must_Include=\\servername\Global\DBconnection\oracle_dwh_db.cfg);

Tags (1)
Comments
Not applicable

Another advantage is the fact that you cando a versioning of single script files via e.g. SVN.

The syntax checker drawback can be overcome by using Notepad++ and a downloadable plugin that adds QV syntax highlighting.

Not applicable

Sometimes syntax checker shows red under lines even though it works fine. So first check your script in qlikview script then create global txt files to use across platform.

Version history
Revision #:
1 of 1
Last update:
‎08-13-2015 10:22 PM
Updated by: