QlikView Reference Manual.pdf - QlikCommunity - QlikView

OtherSymbol
In many cases a way to represent all other values in a table is needed, i.e. all values that were not explicitly
found in the loaded data. This is done with a special variable called OtherSymbol. To define the Other-
Symbol to be treated as ‘all other values’, use the following syntax:
SET OTHERSYMBOL=;
before a load/select statement. may be any string.
The appearance of the defined symbol in an internal table will cause QlikView to define it as all values not
previously loaded in the field where it is found. Values found in the field after the appearance of the Other-
Symbol will thus be disregarded.
In order to reset this functionality use:
Example:
SET OTHERSYMBOL=;
Insert the following statement in the script before the point where the first table above is loaded:
SET OTHERSYMBOL=+;
All references to CustomerIDs other than 1, 2 or 3, e.g. as when clicking on OrderID 1299 will result in
Undefined under Name.
Note!
OtherSymbol is not intended to be used for creating outer joins between tables!!
27.10 NULL Value Handling in QlikView
When no data can be produced for a certain field as a result of a database query and/or a join between tables,
the result is normally NULL values.
The QlikView logic treats the following as real NULL values:
l NULL values returned from an ODBC connection
l NULL values created as a result of a forced concatenation of tables in the QlikView script
l NULL values created as a result of a join statement made in the QlikView script
l NULL values created as a result of the generation of field value combinations to be displayed in a
table box or exported by an export button.
Normally it is impossible to use these NULL values for associations and selections. However, it is possible
to manipulate NULL values at field level, using the nullasvalue statement. See NullAsValue (page 255). Furthermore,
NULL values from ODBC, can be manipulated using nulldisplay (see below).
Text files per definition cannot contain NULL values.
388