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.
concatenate

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

See: Concatenating tables

See: Concatenate

crosstable

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

See: Working with crosstables in the data load script

See: Crosstable

generic

This table is split into several other logical tables.

See: Generic databases

See: Generic

intervalmatch

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

See: Matching intervals to discrete data

See: 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.

See: Combining tables with Join and Keep

See: Join

keep

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

See: Combining tables with Join and Keep

See: Keep

mapping

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

See: Using mapping as an alternative to joining

See: 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.

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!