Table groupings are similar to page groupings- only that here is specified on which amount of nodes the table should display information. All issues described above also apply to tables, except for the page breaks.
The grouping of a table is relative to the page grouping or to the superior element (e.g. another table or the template which called this table). If the table grouping is defined using the "Auto XPATH completion" function, the path from the page grouping to the table grouping is automatically assembled. A little more difficult is the omission of nodes in the XML tree when the starting point is a table or a template and the current place addresses a defined place.
Example:
XML file:
<Publication>
<Product>
<Name>Product 1</Name>
<DefaultPrices>
<DefaultPrice>
<MinQuantity>1</MinQuantity>
<NetPrice>10,80</NetPrice>
</DefaultPrice>
<DefaultPrice>
<MinQuantity>10</MinQuantity>
<NetPrice>9,90</NetPrice>
</DefaultPrice>
</DefaultPrices>
</Product>
<Product>
<Name> Product 2</Name>
<DefaultPrices>
<DefaultPrice>
<MinQuantity>1</MinQuantity>
<NetPrice>7,50</NetPrice>
</DefaultPrice>
<DefaultPrice>
<MinQuantity>10</MinQuantity>
<NetPrice>6,90</NetPrice>
</DefaultPrice>
</DefaultPrices>
</Product>
</Publication>
It is a table over all products, for each product the scaled NetPrices should be displayed.
Definition:
Result:
The difficulty is that it is not clear from where and to where the relative path (DefaultPrices/DefaultPrice) must be built. Currently a copy of the branch (filter/virtual grouping) is used for this problem.
Groupings are also used in list elements; the handling is the same as in tables and page groupings.