Skip to main content Skip to complementary content

System fields

In addition to the fields extracted from the data source, system fields are also produced by Qlik Sense. These all begin with "$" and can be displayed like ordinary fields in a visualization, such as a filter pane or a table. System fields are typically created during script execution, and are primarily used as an aid in app design.

Information note

System fields are not included in field lists in the assets panel or the Expression editor. If you want to use a system field, you need to reference it by typing it manually.

Example: =$Field

Available system fields

The following system fields are available:

Tag Description Can be manipulated in the script
$system

System field that is generated by Qlik Sense during script execution.

See: System fields

No
$key Key field providing a link between two or more tables. No
$keypart The field is part of one or more synthetic keys. No
$syn

Synthetic key

See: Synthetic keys

No

$hidden

Hidden field, that is, it is not displayed in any field selection list when creating visualizations, dimensions or measures. You can still use hidden fields in expressions, but you need to type the field name.

You can use the HidePrefix and HideSuffix system variables to set which fields to hide.

See: HidePrefix

See: HideSuffix

Yes
$numeric All (non-NULL) values in the field are numeric. Yes
$integer All (non-NULL) values in the field are integers. Yes
$text No values in the field are numeric. Yes
$ascii Field values contain only standard ASCII characters. Yes
$date All (non-NULL) values in the field can be interpreted as dates (integers). Yes
$timestamp All (non-NULL) values in the field can be interpreted as time stamps. Yes
$Table Displays all internal tables loaded by the script. No
$Field Displays the fields that are read from the tables. No
$Fields Represent the number of fields in different tables. No
$Rows Displays the position of the fields in the tables. No
$Info Displays the number of rows in the tables. No

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 – please let us know!