Skip to main content
Announcements
Qlik Introduces a New Era of Visualization! READ ALL ABOUT IT
cancel
Showing results for 
Search instead for 
Did you mean: 
robodeveloper
Contributor III
Contributor III

Using common script within multiple apps?

We have several apps used to extract and transform data into QVDs.     These apps contain the same script within their data load editors.   But this script now needs amending and I will have to repeat the process for each app in turn.  

Ideally, I would like to have just one piece of script which our ETL apps could call within their load editor (e.g. like a SAS autoexec file).   So when it came to maintaining the script I would only have to update in one place.

Is there a method to achieve this?

regards,

RB

1 Solution

Accepted Solutions
petter
Partner - Champion III
Partner - Champion III

Yes - you can use the $(include=.......) or better the $(must_include=.....)

https://help.qlik.com/en-US/sense/June2018/Subsystems/Hub/Content/Scripting/SystemVariables/Include....

Note: Whatever the documentation writers in Qlik might think.... The include is NOT a SYSTEM VARIABLE.

It is a directive that includes the contents of a file from the filesystem or an http (URL) address as if the text is a part of the script.

View solution in original post

4 Replies
petter
Partner - Champion III
Partner - Champion III

Yes - you can use the $(include=.......) or better the $(must_include=.....)

https://help.qlik.com/en-US/sense/June2018/Subsystems/Hub/Content/Scripting/SystemVariables/Include....

Note: Whatever the documentation writers in Qlik might think.... The include is NOT a SYSTEM VARIABLE.

It is a directive that includes the contents of a file from the filesystem or an http (URL) address as if the text is a part of the script.

ruanhaese
Partner - Creator II
Partner - Creator II

I take it you have considered changing the process first?

There should only be 1 extract app (for each extraction process) for data in the Extraction process.

The transform should then be based on the QVD's extracted in the previous process.

The "E" & "T" (from ETL)  apps should be separated.

robodeveloper
Contributor III
Contributor III
Author

Thanks!

robodeveloper
Contributor III
Contributor III
Author

Each app is detecting a trigger file to commence ETL apps each for a given data stream.

I hadn't given much thought to the pro's and con's of splitting the E/T steps.    What would be your reasoning to split these out?