The NoConcatenate prefix forces two loaded tables with identical field sets to be treated as two separate internal tables, when they would otherwise be automatically concatenated.
Syntax:
NoConcatenate( loadstatement | selectstatement )
By default, if a table is loaded that contains an identical number of fields and matching field names to a table loaded earlier in the script, Qlik Sense will auto concatenate these two tables. This will happen even if the second table is named differently.
However, if the script prefix NoConcatenate is included before the load statement or select statement of the second table, then these two tables will be loaded separately.
A typical use case for NoConcatenate is when you may need to create a temporary copy of a table to perform some temporary transformations on that copy, while retaining a copy of the original data. NoConcatenate ensures that you can make that copy without implicitly adding it back onto the source table.
Regional settings
Unless otherwise specified, the examples in this topic use the following date format: MM/DD/YYYY. The date format is specified in the SET DateFormat statement in your data load script. The default date formatting may be different in your system, due to your regional settings and other factors. You can change the formats in the examples below to suit your requirements. Or you can change the formats in your load script to match these examples.
Default regional settings in apps are based on the regional system settings of the computer or server where Qlik Sense is installed. If the Qlik Sense server you are accessing is set to Sweden, the Data load editor will use Swedish regional settings for dates, time, and currency. These regional format settings are not related to the language displayed in the Qlik Sense user interface. Qlik Sense will be displayed in the same language as the browser you are using.
| Example | Result |
|---|---|
|
Source: LOAD A,B from file1.csv; CopyOfSource: NoConcatenate LOAD A,B resident Source; |
A table with A and B as measures is loaded. A second table with the same fields is loaded separately by using the NoConcatenate variable. |
Example 1 – Implicit concatenation
Overview
In this example, you will add two load scripts in sequential order.
Open the Data load editor and add the load script below to a new tab.
The load script contains:
-
An initial dataset with dates and amounts that is sent to a table named Transactions.
First load script
Transactions:
LOAD
*
Inline [
id, date, amount
1, 08/30/2018, 23.56
2, 09/07/2018, 556.31
3, 09/16/2018, 5.75
4, 09/22/2018, 125.00
5, 09/22/2018, 484.21
6, 09/22/2018, 59.18
7, 09/23/2018, 177.42
];
Results
Load the data and open a sheet. Create a new table and add these fields as dimensions:
-
id
-
date
-
amount
| id | date | amount |
|---|---|---|
| 1 | 08/30/2018 | 23.56 |
| 2 | 09/07/2018 | 556.31 |
| 3 | 09/16/2018 | 5.75 |
| 4 | 09/22/2018 | 125.00 |
| 5 | 09/22/2018 | 484.21 |
| 6 | 09/22/2018 | 59.18 |
| 7 | 09/23/2018 | 177.42 |
Second load script
Open the Data load editor and add the load script below to a new tab.
The load script contains:
-
A second dataset with identical fields is sent to a table named Sales.
Sales:
LOAD
*
Inline [
id, date, amount
8, 10/01/2018, 164.27
9, 10/03/2018, 384.00
10, 10/06/2018, 25.82
11, 10/09/2018, 312.00
12, 10/15/2018, 4.56
13, 10/16/2018, 90.24
14, 10/18/2018, 19.32
]; Results
Load the data and go to the table.
| id | date | amount |
|---|---|---|
| 1 | 08/30/2018 | 23.56 |
| 2 | 09/07/2018 | 556.31 |
| 3 | 09/16/2018 | 5.75 |
| 4 | 09/22/2018 | 125.00 |
| 5 | 09/22/2018 | 484.21 |
| 6 | 09/22/2018 | 59.18 |
| 7 | 09/23/2018 | 177.42 |
| 8 | 10/01/2018 | 164.27 |
| 9 | 10/03/2018 | 384.00 |
| 10 | 10/06/2018 | 25.82 |
| 11 | 10/09/2018 | 312.00 |
| 12 | 10/15/2018 | 4.56 |
| 13 | 10/16/2018 | 90.24 |
| 14 | 10/18/2018 | 19.32 |
When the script runs, the Sales table is implicitly concatenated onto the existing Transactions table due to the two datasets sharing an identical number of fields, with identical field names. This happens despite the second table name tag attempting to name the result set ‘Sales’.
You can see that the Sales dataset is implicitly concatenated by looking at the Data load progress log.
Data load progress log showing Transactions data being implicitly concatenated.
