QlikView Designer & Developer

Exercises

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Table of contents
Ex. 1: Creating a Connection to the Database
Ex. 2: Loading Data
Ex. 3: Loading Additional Data
Ex. 4: Structuring the Script
Ex. 5: Orders and Order Details
Ex. 6: Loading a Text File in XML Format
Ex. 7: Qualify Statement
Ex. 8: Layout basics
Ex. 9: Sorting Data
Ex. 10: Creating Variables
Ex. 11: Master Calendar
Ex. 12: Adding Excel Files
Ex. 13: Creating Data in the Script
Ex. 14: Creating Quarters
Ex. 15: Reading the Shipments Table: Synthetic Keys
Ex. 16: Circular References
Ex. 17: Charts & Themes
Ex. 18: QVD Generation
Ex. 19: Mapping LOAD
Ex. 20: Cross Tables
Ex. 21: Condition on a Field in a Table
Ex. 22: Aggregation & Joining tables
Ex. 23: Concatenation
Ex. 24: Preceding Load on Preceding Load
Ex. 25: Set Analysis & MiniCharts
Ex. 26: Cyclic Groups
Ex. 27: Advanced Charts
Ex. 28: Buttons & Bookmarks

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 1: Creating a Connection to the Database

1. Start QlikView if it is not already active.
2. Select New from the File menu or the appropriate button on the toolbar to create
a new QlikView document.
3. Select Document Properties from the Settings menu, and open the General tab in
the dialog. Make sure that Generate Log file is checked. This will generate a script
execution log file every time the load script is run.
4. Close the Document Properties and go to the User Preferences in the Settings
menu. On the Save tab, make sure to check the Save Before Reload. This will make
QlikView save all your documents every time before you reload the document so
that you will not lose any changes you have made in the script.
5. Select Use Backup and use 2 instances.
6. Select Save from the File menu or the associated save button on the toolbar to
save a document.
7. Select Edit Script from the File menu or the toolbar. You have now created a new
script file and, as you can see, it already contains some lines of script. These are
the format variables, which are generated automatically by QlikView. The variables
are based on the regional settings in your operating system regarding date,
currency, time, etc.
8. Select OLE DB in the Database group on the Data tab and click Connect to open the
Connect to Data Source dialog. This opens up a dialog where you can choose from
several OLE DB providers that are installed on your computer. Since we are
working with an Access database, we need to select the driver that works with this
database provider.
9. Select the Microsoft Jet 4.0 OLE DB Provider to connect to the Access database.
10. Click Next to get to the dialog page where we can select the database to which we
will connect.
11. Click on the Browse icon (3 points) and browse to the QWT database path. The
QWT database does not have a user name and password so we can leave the
default as it is.
12. Click on Test Connection to check that QlikView connects to the database and then
OK to close the Data Link Properties dialog.
Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 2: Loading Data

1. We will start by adding the Customers table to the script.
2. Click the SELECT button in the Edit Script dialog, and select the table Customers
from Database Tables.
3. The Create Select Statement dialog has several options. In the top section you can
find information on the active database. The middle section holds information
regarding the Tables, Views, Synonyms, System Tables and Aliases of the database.
In a large database, it might be a good idea to uncheck everything but what you
actually want to read into QlikView. Usually, you want to work with Tables and
sometimes Views, but the rest may be unnecessary. When a table is selected, you
can find the fields of the table in the Fields window. You have the option to view
the fields in Text Order or Original Order, i.e. the order they are placed in the table.
There are several ways to view the table currently being read into QlikView in the
bottom of your screen. On the Script tab you can see the syntax as it will appear in
the script. You can select how the fields will be placed in the script, whether in one
Column, on one Row or Structured with line breaks. You also have the possibility to
read the table with a Preceding Load. The preceding load gives you the advantage
of working with the QlikView syntax instead of the SQL syntax.
4. Make sure to check Preceding Load so that we can use the QlikView syntax in the
script.
5. Click OK to close the Create Select Statement dialog.
6. Make a comment before the table so that this table will be easy to find.
// ************** Customers table **************
7. Give the table a label by typing the name Customers on the row above the LOAD
statement and end it with a colon (:). The first few lines of your script should now
look like this:
//************** Customers table **************
Customers:
LOAD Address,
8. Click the Reload icon in the Edit Script dialog to reload the script.
9. Do the same procedure with the Shippers table.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

10. As you can see, the Shippers table has a field name in common with the Customers
table. The field CompanyName exists in both tables. In QlikView, any filed with the
same name will be linked. This field should not be a key field between these two
tables. We have to rename this field in one of the tables to avoid a connection
between these two tables. Put the cursor directly after CompanyName in the
Shippers table and rename this field to Shippers using the word AS. The script
should look like the following:
// *************** Shippers table ***************
Shippers:
LOAD CompanyName as Shippers,
ShipperID;
SQL SELECT *
FROM Shippers;
11. Save the document and Reload the script.

Ex. 3: Loading Additional Data

1. In this exercise we will bring in additional tables needed from the QWT.mdb
database. Disregard the connection or associations between the tables for now,
these will be added later on in the course.
2. Load the Products table into the script. Make sure to load all fields except the
UnitPrice since this field will be loaded from another table later on (load the
complete table and then erase that line). Make a comment about the table and
label it Products.
3. Load the fields from the Categories table into the script. Make a comment about
the table and label it Categories.
4. Load the fields from the Divisions table into the script. Make a comment about the
table and label it Division.
5. Save and Reload.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 4: Structuring the Script

1. Open the script using the Edit Script icon.
2. Click on the Add new tab tool button or go to the Tab Menu and click Add Tab
3. Name the tab Dimensions.
4. Go to the Main tab and select all the tables we have loaded so far. Leave the Set
statements and the Connect statement for now.
5. Cut the tables and go to the Dimensions tab.
6. Paste the tables in the Dimensions tab.
7. Save the document

Ex. 5: Orders and Order Details

1. In the Script Editor, create a new Tab and name it Orders.
2. Click SELECT again and load the table Orders.
3. Next, we will load the table OrderDetails under the Orders table. Here we will
create a new field LineSalesAmount, which is Unit-Price*Quantity*(1-Discount).
The load script should look like this:
//*************** Order Details table***************
OrderDetails:
LOAD Discount,
LineNo,
OrderID,
ProductID,
Quantity,
UnitPrice,
UnitPrice * Quantity * (1 - Discount) AS LineSalesAmount;
SQL SELECT * FROM [Order Details];
4. Save the document and Reload the script.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 6: Loading a Text File in XML Format

1. Open the Edit Script dialog from the menu or toolbar.
2. Position your cursor at the bottom of the Dimensions tab, and add a comment for
the Suppliers data table load.
3. Click the Table Files button to open the Table Files: Open Local Files dialog.
4. Browse to the file suppliers.xml in the folder DataSources and click Open.
5. Press Next to see how QlikView interprets the XML.
6. Select the Tables tab to see what tables the XML file contains.
7. Click Finish.
8. Clean the script. It should look like this:
//*************** Suppliers ***************
Suppliers:
LOAD SupplierID,
CompanyName,
ContactName,
Address,
City,
PostalCode,
Country,
Phone,
Fax
FROM ..\Datasources\Suppliers.xml (XmlSimple, Table is
[Suppliers/_empty_]);
9. Save and Reload

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 7: Qualify Statement

1. If you have problems with the names of your data sources you can automatically
rename them using the QUALIFY statement.
2. Enter the following lines of code before the suppliers table LOAD. As SupplierID is
to be connected to another table, it should not have the table qualifier. This is
specified using the statement UNQUALIFY.
QUALIFY *;
UNQUALIFY SupplierID;

3. After the Suppliers table has been loaded, we must add the following statement so
that all the fields loaded after this one do not have the table qualifier.
UNQUALIFY *;
4. Save and Reload the document.
5. Open the Table Viewer. You will now see the results of adding the table name to
the field name.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 8: Layout basics

List Box
The list box is the most basic sheet object on the screen. It contains a list of all the possible
(distinct) values of a specific field. In a list box you often make selections and look at logical
connections and associations.

Table Box
Think of a table box as a combination of list boxes. Instead of placing each field in its own object
separately, however, the table box combines them. The content of every row is logically connected.
The columns may be fetched from different input tables, allowing the creation of tables from any
possible combination of input tables.

Multi Box
A multi box is like a set of dropdown list boxes gathered within the same frame. Every field is
represented by a row in the multi box. Multiple fields can be combined into a single multi box.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Search Object
Search objects can be used for searching for information anywhere in the document. W e can select
certain fields or tables or allow a full search across the document.

Current Selections
The current selections box displays the selection status of your document. It is a good idea to place
a current selections box on every sheet in your application. The current selections box lists all fields
where selections have been made as well as the selected values or if there are too many of them
to display in the space allocated the number of selected values.

Text Object
Text objects are used for adding information to a QlikView document. They can be used to show
text information or an image in the layout. They can be moved and positioned anywhere on a sheet,
just like any other sheet object. Text objects can also be used effectively for displaying the results of
calculations, and to create backgrounds, borders and titles for groups of objects on a QlikView
page.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 9: Sorting Data

1. Open the Edit Script dialog and go to the Orders tab.
2. Sort the Orders table by typing the following at the end of the SELECT statement
before the semicolon.
ORDER BY OrderDate ASC;
3. The script should look as follows after you have added the Order By statement.
//*************** Orders table ***************
Orders:
LOAD
CustomerID,
EmployeeID,
Freight,
OrderDate,
OrderID,
ShipperID;
SQL SELECT *
FROM Orders
ORDER BY OrderDate ASC;
4. The ORDER BY statement sets the sort order of the table. You can use one or more
fields in the statement to specify how the table should be sorted. The fields will be
sorted in the order shown with the first field having priority if you have more than
one field. Commas should separate the fields. You can also decide if you want to
sort the fields Ascending or Descending by typing Asc or Desc after the last field.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 10: Creating Variables

1. Create a new tab in the script and call it Calendar.
2. Create a new variable for the first date by typing the following script statement.
LET varMinDate = Num(Peek('OrderDate', 0, 'Orders'));
3. When creating a variable in QlikView, a SET or a LET statement is often used to
define the variable. The SET statement is used when you want a variable to hold
the string or numeric value that is to the right of the Equal (=) sign. The LET
statement is used when you need to evaluate what is to the right of the Equal sign.
4. Create a second variable for the last date by typing the following statement.
LET varMaxDate = Num(Peek('OrderDate', -1, 'Orders'));
5. Create a third variable for today by typing the following statement.
LET varToday = num(today());
6. Create a new table by typing the following script into the Script Editor.
//*************** Temporary Calendar ***************
TempCalendar:
LOAD
$(varMinDate) + rowno() - 1 AS Num,
date($(varMinDate) + rowno() - 1) AS TempDate
AUTOGENERATE
$(varMaxDate) - $(varMinDate) + 1;
7. The AUTOGENERATE statement creates the table where the numbers of rows
created are dependent on the number of days between the min and the max date.
8. Save and Reload the script.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 11: Master Calendar

1. Open up the script editor again and put the cursor under the Temporary Calendar
2. Create a MasterCalendar table referring to the script shown below.
//*************** Master Calendar ***************
MasterCalendar:
LOAD TempDate AS OrderDate,
Week(TempDate) AS Week,
Year(TempDate) AS Year,
Month(TempDate) AS Month,
Day(TempDate) AS Day,
Weekday(TempDate) AS WeekDay,
Date(monthstart(TempDate), 'MMM-YYYY') AS MonthYear,
Week(TempDate)&'-'&Year(TempDate) AS WeekYear
RESIDENT TempCalendar
ORDER BY TempDate ASC;
3. You will notice we had to rename the TempDate field to OrderDate to get a
connection to the Orders table.
4. Erase the TempCalendar table by typing:
DROP TABLE TempCalendar;

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 12: Adding Excel Files

1. Add a new tab and name it FileData.
2. Go to the Data From Files grouping at the bottom of the Data tab.
3. Make sure that the Relative Paths check box is checked.
4. Click the Table Files button to open the Open Local Files dialog.
5. Browse to the file EmpOff.xls in the folder DataSources and click Open.
6. Select Embedded Labels.
7. Click on the field name EmpID and change the name to EmployeeID.
8. Click Finish.
9. Now, add your comments to this data load, and label the table as Employee. You
can also delete the Directory; statement, which is generated because of the
Relative Paths specification. We will not need these statements in our script.
10. In addition to the work we have completed so far, we need to provide an
[Employee Hire Year] field. Add this field now, using the Year function on the [Hire
Date] field. Name the new field HireYear.
11. Now, follow the same procedure for the Office data. This table is located in the
second worksheet of the Excel file EmpOff.xls. When you open the File Wizard, be
sure to select the Excel spreadsheet Office$ in the box labelled Table on the first
page of the wizard.
12. Name the table as Offices
13. Save and Reload

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 13: Creating Data in the Script

1. Find the Employees table on the File Data tab and replace the fields First Name
and Last Name with the following statement:
[First Name]&' '&[Last Name] AS Name,
2. Add a new tab to the script and name it SalesPerson.
3. Copy the following scripts:
//************** SalesPersons table**************
SalesPersons:
LOAD
EmployeeID,
Name AS SalesPerson,
Title AS SalesTitle
RESIDENT Employee;
4. Add the following script line in the Orders table LOAD statement immediately after
the loading of the EmployeeID field.
EmployeeID as EmployeeSalesID,
5. Create a new WHERE condition to use the QlikView exists function.
SalesPersons:
LOAD EmployeeID,
Name AS SalesPerson,
Title AS SalesTitle
RESIDENT Employee
WHERE exists(EmployeeSalesID, EmployeeID);
6. The condition in the Where clause checks that the loaded data has matching values
in the field EmployeeSalesID. As the name implies, the exists function can be used
to check whether a specific field value exists in a specified field of the data loaded
so far. Remember to be careful of the order of your script statements, since the
reference field should be populated prior to checking for values. In this example,
the Orders table must be loaded prior to the Sales_Person table for this condition
to work properly.
7. Save and Reload

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 14: Creating Quarters

1. Position your cursor after the Connect statement on the Main tab.
2. Add the following statement to the script:
Quarters:
LOAD* INLINE [
Month, Quarter
1,Q1
2,Q1
3,Q1
4,Q2
5,Q2
6,Q2
7,Q3
8,Q3
9,Q3
10,Q4
11,Q4
12,Q4];
3. Notice that a load inline contains the field names and data enclosed by square
brackets ([]). Also notice the field names are located on the first line, and that data
values are separated by commas. The table entered in the script associates
numeric months to the corresponding quarter. When we run the script, a new field
(Quarter) is generated.
4. Save and Reload the document.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 15: Reading the Shipments Table: Synthetic Keys

1. Go to the Script Editor and go to the bottom of the Dimensions tab.
2. Click Select to go to the Create Select Statement dialog. Select the Shipments table
and read all fields into the QlikView document with a preceding load.
3. Save and Reload the document.
4. Open up the Table Viewer and notice that there is a new table called $Syn. This is a
Synthetic table and can drastically affect the performance of QlikView
5. In the Shipments table comment the field ProductID.
6. Create a composite field of OrderID and LineNo using the & to concatenate the
fields. Make sure to put a separator in between the fields as well. Name the key
field OrderLineKey.
7. Use the autonumber function to get a number instead of text for the key field. This
is especially useful when working with large tables since numeric values takes up
less memory than text values. Comment the fields OrderID and LineNo. This is
necessary to avoid the synthetic key and have only one (OrderLineKey) connecting
field between the Shipments and the OrderDetails tables. The script should look
as follows:
//*************** Shipments table***************
Shipments:
LOAD CustomerID,
EmployeeID,
//LineNo,
//OrderID,
autonumber(OrderID &'-'& LineNo) as OrderLineKey,
//ProductID,
ShipmentDate,
ShipperID;
SQL SELECT *
FROM Shipments;
8. Create the same OrderLineKey field in the OrderDetails table.
autonumber(OrderID &'-'& LineNo) as OrderLineKey
9. Save and Reload the script.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 16: Circular References

1. Open up the Table Viewer and arrange the tables for easy viewing. As can be seen,
we have a circular reference between the Orders, Shipments and OrderDetails
tables. We are going to get rid of this circular reference.
2. According to the client, all the fields that are common between the Shipments
table and the Orders table originate in the Orders table; therefore, in our QlikView
document it is safe for us to just comment or remove these fields from the
Shipments table. We can do this because of the data structure of our data. If not
all values existed in the Orders table, we would have had to use another solution
to the problem with the circular reference.
3. Go to the Script Editor and find the table Shipments.
4. Comment out the fields CustomerID, EmployeeID, ProductID and ShipperID. Make
sure that the commas and semi colon are correct.
5. Save the document and Reload the script.
6. Open the Table Viewer and look at the result. The circular reference should have
disappeared and there should be no synthetic keys.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 17: Charts & Themes

1. Create a new Tab
2. Select Document Properties in the Settings menu. Go to the Layout tab and click
Apply Theme. Select the theme you like and click OK.
3. Insert a Current Selections Box and the following List Boxes:
Country
Product Name
Company Name
Name
Month
Year
4. Click on the Create Chart icon.
5. Select these fields in each tab:
Tab
General
Dimensions
Expressions

Sort
Presentation
Number

Profesionales en Manejo de Datos S.A. de C.V.

Actions
Type Sales Country in the Window Title field
Choose the Pie Chart icon
Add Country
Label: Sales
Definition: sum(LineSalesAmount)
Check the Relative Box
Check Y-value and select Descending
Maximum Number of Slices: 7
Check Show Numbers in Legend
Fixed to: 2 Decimals

www.pmd.com.mx

| Exercises

Ex. 18: QVD Generation

1. Locate the Customers load statement on the Dimensions tab
2. Following the Customers table LOAD statement, add the STORE statement as
follows:
STORE Customers into
Datasources/Customers.qvd;
3. Click OK and then save your file. Reload the script. You will not notice any changes
to the System sheet in your application. No new logical tables or fields exist. The
STORE statement you just added has no effect on your current QlikView document,
other than executing an additional script statement. Once this statement has
executed, however, a new data file exists that may be read by this QlikView
document, or any QlikView document with access to the folder which we placed
the customers.qvd file.

Ex. 19: Mapping LOAD

1. Change the name of the Quarters Table to Quarters_Map. This is only for knowing
that the table is going to be mapped (good practice).
2. On the next line, type MAPPING in front of the LOAD statement.
3. Do not save and close just yet. If you reload the data now, you will lose the
Quarters table and field, since mapping tables are temporary. However, we can
use the Quarters_Map table in our script. To do this, we will use the applymap
function.
4. Add an applymap function to the Orders table, based on the numeric value of
Month. This function should refer to the Quarters_Map table. Refer to the syntax
example that follows:
applymap('Quarters_Map',num(month(OrderDate)), null()) AS Quarter
5. Save and Reload
6. Check the results in the Orders table

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 20: Cross Tables

1. Open the Edit Script dialog.
2. Create a new tab following the Sales Person tab and call it Budget.
3. Click on the Table Files button and open the Budget.xls file.
4. In the File Wizard, start by setting the Header Size to one line.
5. Next, we need to make sure that there are no empty rows in the Office field. Click
on the Next button and then click on Enable Transformation Step to transform the
table.
6. Click the Fill button (Fill tab) and then Cell Condition. We want the cell to fill if it is
empty. Click OK, OK and Next to return to the File Wizard.
7. Click on Crosstable to change the table from a cross table to a normal table.
8. Click on the Qualifier Fields and type 2 to expand them to include both the Office
and EmployeeID fields in purple.
9. A qualifying field in a cross table, is a field that should not be altered during the
Cross table load. 2005 is not a qualifying field. This is the first of the fields we want
to transform so that the years are placed in one field and the budget values are
placed in another field.
10. Name the Attribute BudgetYear.
11. Name the data BudgetAmount.
12. Click Finish.
13. Name this table Budgets.
14. Save and Reload the document.
15. Open the Table Viewer. As you can see, there is a synthetic key between the
Budgets and the Employees table. We want to remove this synthetic key. All
values in the Budget table for Office and Employees should be in the Employees
table. This means that we can resolve this synthetic key by concatenating the fields
involved into a key field, and just keep them in the Employees table.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

16. Go to the Script Editor.

17. Change the Budget table to the following script. Make sure you change the
CROSSTABLE statement to have only one qualifying field.
Budgets:
CROSSTABLE(BudgetYear, BudgetAmount, 1)
LOAD Office&'-'&EmployeeID AS BudgetKey,
[2005],
[2006],
[2007],
[2008],
[2009]
FROM ..\Datasources\Budget.xls
(biff, header is line, embedded labels, table is
[Sheet1$], filters(Replace(1, top, StrCnd(null))));
18. Go to the File Data tab and add the following line to the top of the Employees
table.
Office&'-'&EmpID AS BudgetKey,
19. Save and Reload the script.

Ex. 21: Condition on a Field in a Table

1. Open the Edit Script dialog and go to the Dimensions tab.
2. Find the Categories table and place the cursor after the last field of this table.
3. Type a comma and press ENTER to get to a new row. Type the following to create
the CategoryType field.
IF(CategoryID = 5 OR CategoryID = 6, 'Footwear', 'Clothing') AS
CategoryType;
4. Save the script and Reload.
5. Look at the fields. You can now see that we have a new field named CategoryType.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 22: Aggregation & Joining tables

1. Open the Script Editor and place the cursor after the OrderDetails table on the
Orders tab.
2. Add the following statement to your script:
LOAD OrderID,
sum(LineSalesAmount) AS OrderSalesAmount
RESIDENT OrderDetails
GROUP BY OrderID;
3. Notice the aggregation function sum(LineSalesAmount) included in this statement.
This function will be evaluated over all the potential combinations of the other
fields in the LOAD (OrderID) statement. The GROUP BY clause is needed to
aggregate or group fields other than those included in the aggregation. In this case,
it will total the Sales Amount for each OrderID.
4. Place the cursor just in front of LOAD in the table just created.
5. Type LEFT JOIN (Orders) in front of the LOAD statement. The result should be as
below.
LEFT JOIN (Orders)
LOAD
6. Here we use a LEFT JOIN load because we want to make sure that we do not get
any values of Orders that do not exist in the Orders table. In QlikView, the default
join behavior is a full outer join. Therefore, if there are no matching fields between
the two joined tables, you will get a Cartesian product of the records. Since we are
specifying OrderID in both tables, and we are specifying Left, only the records
matching OrderID included in the Orders table will be included. We include the
OrderSalesAmount field because that is what we want to add to the Orders table.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 23: Concatenation

1. In this exercise we will add new Employees to our existing table form an Excel file.
Position your cursor on the File Data tab directly after the Employees table has
been loaded.
2. Load the new Excel file and modify the LOAD statement to be the same of our first
Employee table.
3. Click OK and Save the QlikView document.
4. Run the script.
5. You may not notice any difference in the Table Viewer, this is because if we load a
new table with the same structure as a Resident one, QlikView will automatically
concatenate them. If you do not have the exact same structure and you want to
force the concatenation, use the CONCATENATE prefix.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 24: Preceding Load on Preceding Load

1. In the Main tab create the following table either by typing it from scratch or by
using the Select button.
UnitCost_Map:
MAPPING LOAD
ProductID,
UnitCost;
SQL SELECT *
FROM Products;
2. Go to the Orders tab and add the following script line to the bottom of the
OrderDetails table just above the SQL SELECT * line. Remember to remove the
semi-colon from the line above and replace it with a comma.
applymap('UnitCost_Map', ProductID, 0) * Quantity AS CostOfGoodsSold;
3. We combine the applymap function with a calculation and create the
CostOfGoodsSold field directly in the preceding LOAD of the OrderDetails table.
4. The last of the key measures that we need is the Margin. The Margin is calculated
as the LineSalesAmount CostOfGoodsSold. The easiest way to do this is to place a
preceding load on top of the preceding load in the OrderDetails table. You can add
several preceding loads on top of each other and they will be evaluated from the
bottom and up. This means that you can use a field created in a preceding load in a
new preceding load on top of the first one.
5. Put the cursor after the OrderDetails label.
6. Create a preceding load by adding the following script.
LOAD
LineSalesAmount - CostOfGoodsSold AS Margin,
*;

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

7. The full OrderDetails script should look like this:

//*************** Order Details table***************
OrderDetails:
LOAD
LineSalesAmount - CostOfGoodsSold AS Margin,
*;
LOAD Discount,
LineNo,
OrderID,
ProductID,
Quantity,
UnitPrice,
UnitPrice * Quantity * (1 - Discount) AS LineSalesAmount,
autonumber(OrderID &'-'& LineNo) as OrderLineKey,
applymap('UnitCost_Map', ProductID, 0) * Quantity AS CostOfGoodsSold;
SQL SELECT * FROM [Order Details];
8. Save and Reload the script.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

Exercises

Ex. 25: Set Analysis & MiniCharts

1. Create a new page in your document
2. Create a Straight Table chart that displays a comparison of annual sales by
CompanyName based on the year selected by the user.
3. Using CompanyName as Dimension, create the following three expressions:
Label
=Only(Year)
=Only(Year)-1
=Only(Year) & ' vs ' &
(Only(Year)-1)

Expression
Sum({$<Year={$(=Only(Year))}>} LineSalesAmount)
Sum({$<Year={$(=Only(Year)-1)}>} LineSalesAmount)
Sum({$<Year={$(=Only(Year))}>} LineSalesAmount) Sum({$<Year={$(=Only(Year)-1)}>} LineSalesAmount)

4. On the Visual Cues tab, make the negative values for the year-to-year comparison
red and the positive values green.
5. Return to the General tab and add a Calculation Condition to ensure that the user
selects a Year to begin the comparison by entering the following into the
Calculation Condition box:
Count(distinct [Year])=1
6. Click on the Error Messages button on the General tab and then on Calculation
Condition Unfulfilled in the Standard Messages list.
7. Type Select a Year to compare with a previous year in the Custom Message box
and click OK.
8. Create a new expression and name it Trend
=sum({1}LineSalesAmount)
9. In the Display Options choose Mini Chart and click the Mini Chart Settings button
10. Select Year as the Dimension and Sparkline as the Mode.
11. Save your file

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 26: Cyclic Groups

1. Go to Document Properties in the Settings menu
2. In the Groups tab, click New and select Country, CompanyName and Name as
fields.
3. Choose the Cyclic Group option and name it My Group
4. Create a Straight Table Chart with the new group as Dimension and the following
expressions:
Label
Sales

Expression
=sum(LineSalesAmount)

# orders
Margin

=count(OrderID)
=sum(Margin)/sum(LineSalesAmount)

Avg per order

=Sum(LineSalesAmount)/Count(DISTINCT
OrderID)

5. A Cyclic Group is used to check the same expressions over multiple dimensions
(one at a time). In the chart there is a button next to the dimension label. If you
click it, you can change between country, company and Sales person and analyze
its sales data.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

Ex. 27: Advanced Charts

Combo Chart
1. Create a new tab and name it Advanced Charts
2. In the new tab, create a new Combo Chart
3. Choose My Group as dimension and add the following expressions:
Label
Sales
Margin
Margin %

Expression
=sum(LineSalesAmount)
=sum(Margin)
=sum(Margin)/sum(LineSalesAmount)

4. In the Display Options Group in the Expressions tab select:

Expression
Sales
Margin
Margin %

Display Options
Bar
Line
Symbol (Cross)

5. In the Presentation tab set the Max Visible Number to 7

6. In the Axes tab click in the Margin % expression and select Right (Top) in the
Position group

Radar Chart
7. Create a new Radar Chart with Month as dimension and sum(LineSalesAmount) as
the expression. This will represent the distribution of the sales in different months.

Gauge
8. Create a new Gauge Chart
9. In the Show Title in Chart textbox (General tab) type:
=num(sum(Margin)/sum(LineSalesAmount)*100, '0.00%')

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx

| Exercises

10. Click Next in the Dimension tab (Gauges are dimensionless charts) and for the
expression type:
=sum(Margin)/sum(LineSalesAmount)
11. In the Presentation tab set the Max value to .3, uncheck the Autowidth Segments
option and specify the following segments:
Segment
Bad
Medium
OK

Color
Red
Yellow
Green

Lower Bound
0.0
0.05
0.1

Cyclic Charts
12. Return to the Sales Tab and go to the pie chart properties.
13. In the General Tab check Pie Chart and Block Chart.
14. There is a new icon in the charts caption. If you click it, the chart with toggle
between the types selected.
Ex. 28: Buttons & Bookmarks
1. Create a new Button Object.
2. In the name textbox type Clear .
3. In the next tab add a new action: Selection Clear All.
4. There are a number of different actions, try some of them.
5. Insert a new Bookmark Object.
6. Make any selections and click Add Bookmark.
7. Every time you select that bookmark those selections will be presented.

Profesionales en Manejo de Datos S.A. de C.V.

www.pmd.com.mx