Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content

Logical tables

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.
Logical tables
Table Description
concatenate

This table is concatenated with (added to) another named table or with the last previously created logical table.

For more information, see Concatenating tables and Concatenate.

crosstable

This table is unpivoted. That is, it is converted from crosstable format to column format.

For more information, see Working with crosstables in the data load script and Crosstable.

generic

This table is split into several other logical tables.

For more information, see Generic databases and Generic.

info

This table is not loaded as a logical table, but as an information table containing links to external information such as files, sounds, URLs, etc.

 

intervalmatch

The table (which must contain exactly two columns) is interpreted as numeric intervals, which are associated with discrete numbers in a specified field.

For more information, see Matching intervals to discrete data and IntervalMatch.

join

This table is joined by Qlik Sense with another named table or with the last previously created logical table, over the fields in common.

For more information, see Combining tables with Join and Keep and Join.

keep

This table is reduced to the fields in common with another named table or with the last previously created logical table.

For more information, see Combining tables with Join and Keep and Keep.

mapping

This table (which must contain exactly two columns) is read as a mapping table, which is never associated with other tables.

For more information, see Using mapping as an alternative to joining and Mapping .

semantic

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.

For more information, see Semantic.

When the data has been loaded, the logical tables are associated.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!