Each LOAD or SELECT statement generates a table. Normally, Qlik Sense treats the result of each one of these as one logical table. However, there are a couple of exceptions from this rule:
- If two or more statements result in tables with identical field names, the tables are concatenated and treated as one logical table.
- If a LOAD or SELECT statement is preceded by any of the following qualifiers, data is altered or treated differently.
This table is concatenated with (added to) another named table or with the last previously created logical table.
See: Concatenating tables
This table is unpivoted. That is, it is converted from crosstable format to column format.
This table is split into several other logical tables.
See: Generic databases
The table (which must contain exactly two columns) is interpreted as numeric intervals, which are associated with discrete numbers in a specified field.
This table is joined by Qlik Sense with another named table or with the last previously created logical table, over the fields in common.
This table is reduced to the fields in common with another named table or with the last previously created logical table.
This table (which must contain exactly two columns) is read as a mapping table, which is never associated with other tables.
This table is not loaded as a logical table, but as a semantic table containing relationships that should not be joined, e.g. predecessor, successor and other references to other objects of the same type.
When the data has been loaded, the logical tables are associated.