QlikView Reference Manual.pdf - QlikCommunity - QlikView

Note that Tab2 shown here is a table box and not the table itself. The table box will show all possible combinations
between the fields of its columns. Since there is no logic between fields A and C all combinations
of their respective possible values are shown.
Avoid Circular Reference
The next example shows how loosely coupled tables can be useful for avoiding circular references in the
data structure:
This data structure is actually not a very good one since the field name Country is used for two different purposes.
In one table it indicates where the car owner lives and in another it shows where the car manufacturer
resides. With the data in the tables an impossible logical situation is faced. Wherever a selection is made, it
is possible to follow associations leading through every single cell in all three tables.
A decision whether the home country or the car manufacturing country is most important has to be made. If
the Carmaker table is loosely coupled, the associations from Cadillac to USA and from Volvo to Sweden
will be broken. By clicking Sweden it will associate with Björn Borg and Cadillac. By clicking Volvo it
will associate with George Bush and USA.
If it is prefered to concentrate on car manufacturers it would make sense to make the Home table loosely coupled
instead.
Another Example
Let us have a look at another common situation where loosely coupled tables can be useful. Below three
tables are found in a rather typical structure: one transaction table and two dimension tables associating to it
via one field each.
Now, let us say a pivot table showing sales per year and product group is wanted. If we just create one
beside two list boxes showing the dimension fields it will look like this:
119