QlikView Reference Manual.pdf - QlikCommunity - QlikView

'Predecessor' as Relation2
from presdnts where No > 1;
The presidents example is just one simple example of how to use semantic links. These can also be used in
genealogy, where the semantic links can be e.g. cousin, sibling, grandmother, etc. or for people in companies
where the semantic links can be e.g. superior, reports to, secretary, etc.
Example: Using the related values as relation names
Sometimes it is more descriptive to use the related field value as name of the relation. In the case of the presidents,
you may want all the predecessors in one column and all the successors in another:
To create these links, the following script is needed:
Load
No as DuplicateOfNo,
FirstName & ' ' & LastName as Name,
*
from presdnts.csv;
Semantic Load
No -1 as No,
FirstName & ' ' & LastName as Successor,
No as DuplicateOfNo,
'Dummy1'
from presdnts.csv where No > 1;
Semantic Load
No +1 as No,
FirstName &' ' & LastName as Predecessor,
No as DuplicateOfNo,
'Dummy2'
from presdnts.csv;
When a semantic link is clicked, a selection is made in the field of the third column, DuplicateOfNo, which
in the semantic table is always the number of the president shown on the semantic link.
It may not be obvious at first, but the inverse relations in the above construction are almost useless. They
would show a name of a president and, when clicked, select the predecessor/successor of the shown president.
This is why they are called Dummy1 and Dummy2 and only the first relation (column two) is used.
Since we do not want the dummy relations to appear in the list boxes, we must treat the second and fourth
columns as different types of relations. This means that the first and third columns must have different field
384