In some special situations, you might want to disconnect some data from the normal QlikView logic. You can use loosely coupled tables to restrict selections in one field to propagate through to the other fields in the table.
To set a table to be loosely coupled, open the Document Properties dialog and select the Tables tab.
This chapter includes some examples of how loosely coupled tables alter the QlikView logic.
Each of the following three table boxes represents a table read into QlikView:
If the value 2 is selected in field B the following will happen:
The selection ripples through all tables, and excludes values that are not associated.
Now, let's keep this selection but make
The three tables below are found in a rather typical structure: one transaction table and two dimension tables associating to it via one field each.
You can visualize sales per year and product group using a pivot table. Next to the pivot table, two list boxes show the dimension fields:
Even though this is a correct pivot table, the effects of QlikView's logic could now potentially lead to undesired results. If the year 2012 is selected, you get the following result:
Product group Z is no longer visible in pivot table. This is natural, since the value Z in the field
In some sense, the two fields
Note that the selection in the Year list box does not render any value in the