ATiDD Summary Sheet
Advanced Transformations in Script
Different Load types
• from a file
• from data defined in the script
• from a previously loaded table
• from a web page
• from the result of a subsequent Select statement
• from scratch, by generating data automatically
• from analytic connections
Load statement syntax
LOAD [ distinct ]
fieldlist
[( from file [ format-spec ] | from_field
fieldAsSource [format-spec] | inline data [
format-spec ] | resident table-label |
autogenerate size ) | extension
pluginname.functionname([script]
tabledescription)]
[ where criterion | while criterion ]
[ group by groupbyfieldlist ]
[ order by orderbyfieldlist ]
Subroutines in Qlik
Qlik allows you to define you own formulas using
Subroutines.
• Subroutines are reusable pieces of code that can
be defined in the script and called as many times
as needed in the script.
• You define the code and the parameters in them. A
subroutine does not need to have parameters if not
needed.
• Subroutines simplify the script and make the code
easier to maintain and debug.
Load statement prefixes
Qlik prefixes can be applied in any type of load statement.
Some prefixes allow table and data transformations.
• CrossTable: Used to transform cross tables into straight
tables.
Crosstable (attribute_field_name, data_field_name [
, n ] ) Load/ Select * from PivotTable;
• Generic: Used to load generic tables (tables that
represent element properties in a table form).
Generic LOAD/SELECT * from GenericTable1;
• Hierarchy: Used with parent-child hierarchy tables. This
prefix transforms these tables into tables where all the
hierarchy represented as levels.
• HierarchyBelongsTo: Similar to Hierarchy prefix, but in
this case the resulting table contains all ancestor-child
relations of the hierarchy.
Hierarchy (NodeID, ParentID, NodeName, [ParentName],
[PathSource], [PathName], [PathDelimiter],
[Depth])(loadstatement | selectstatement)
• Semantic: Loads tables containing relations between
records.
Semantic SELECT/LOAD Object1 as Object, Relation1 as
Relation, Object2 as Object , Relation2 as Relation
from table1;
Subroutine example in Qlik
SUB LoadAndStore (TableName, TablePath, QVDPath)
LOAD * From $(TablePath)$(TableName).csv;
STORE $(TableName) INTO $(QVDPath)$(TableName).qvd;
LET vRowCount = Num(NoOfRows('$(TableName)'),'#,##0');
TRACE --'$(TableName)' row count: $(vRowCount);
END SUB
// Loading data tables
CALL LoadAndStore ('Sales', '..\Data\','..\QVDs\')
Advanced Transformations in script
Script execution flow controls
• In some cases, there is a need to control the flow of execution and
change it, in order to load more complex file or table structures,
execute external function, loop through field values or tables in the
app, etc.
Some examples that require the usage of flow controls in the script are
the following:
• Loading cross tables with more than one pivoting dimension.
• Loading tables divided in separate files (or worksheets) that need to
be loaded as a single table.
• Stopping script execution at any given point (early termination of the
script execution after a specific script point).
• Generating information tables and metadata of the current tables and
fields.
• Generating QVD files or other exported formats based on the current
tables and fields loaded into the script.
• Creating complex calculations in tables that require recursive
iterations.
• Iterating through the values of a field.
• Creating a piece of code that can be reusable and applicable with
different parameters by using a subroutine.
To control the execution flow in the script, you can use the following:
• Loops - recurrent execution of a piece of code several times.
• Do…While
• For…Next
• For Each…Next
• IF statements - decision trees to evaluate certain conditions and
execute a piece of code or another.
• Switch Case - decision branches based on a result.
• Subroutines - reusable piece of code that can be defined with
parameters and can be executed using a call function as many times
as needed. This allows you to create your own custom functions. 1
• Exit script statement - script termination at any point of the script.