QlikView Reference Manual.pdf - QlikCommunity - QlikView

Even though this is a correct pivot table, the effects of QlikView's logic could here potentially lead to undesired
results. If we select the year 2000 the layout will look as follows:
Product group Z is "gone". This is natural since the value Z in the field ProdGrp has been excluded by the
selection of the value 2000 in the field Year. However, the boss is likely to want Z in the chart with a 0 in
the sum(Amount) column, so that it is clear to everyone that product group Z exists and that nothing has
been sold in 2000.
One could argue that the two fields Year and ProdGrp really have nothing to do with each other and therefore
should not interact just because they happen to be associated via the Trans table. So let's fix that by
declaring the Trans table as loosely coupled. Immediately our little layout will have the following look of:
The table looks like we want it to look. Note that the selection in the Year list box does not render any
value in the ProdGrp list box excluded.
As a summary can be said that this situation, with one or more transaction tables surrounded by a number of
dimensions which should not be excluded, is quite common. Loosely coupled tables is one possible way of
handling such cases.
Loosely Coupled Tables and Subtotals
When using loosely coupled tables in combination with non-hierarchical dimension data subtotals in pivot
tables may become incorrect. The example below is very similar to the previous example, but product B now
belongs to two product groups, X and Y. The product D has disappeared and that sale is now product B
instead.
120