Using Advanced Techniques with Tables

Tables need to be output in exactly the same structure in which they are filled. If there is a need for another representation another data view structure for the same basic data is necessary.

For example, it should be possible to group data records that have the same value in a sort field. Grouped data records that have certain identical values are called control levels. The only way to group data records is by using these control levels from another data view node and then dragging and dropping the table from this node from the Data View to the layout. As a data view can only be created by SAP the customer depends on whether SAP offered this option or not.

A control level contains all the records of the internal table that have the same value in the sort field. For example, all the records of an airline carrier belong to one control level. A table with control levels can look like a nested table.

An example of a nested table:

Tables need to be output in exactly the same structure in which they are filled. If there is a need for another representation another data view structure for the same basic data is necessary.

For example, it should be possible for a table of connections to get for a connection record a list of all flight dates, This would require a nested table. The only way to receive data records with such a nested structure is by using a corresponding data view node and then dragging and dropping the table from this node from the Data View to the layout. As a data view can only be created by SAP the customer depends on whether SAP offered this option or not.

In some cases, it might be more suitable to switch off the Table Creation Wizard and create a hierarchy of subforms that look like a table with more manual effort. This is especially true if you want a multi-line layout (multiple lines for one data row) or a very free and uncommon layout.

You can do this as follows:

1. Switch off the Table Creation Wizard.
2. Drag-and-drop the table source from the Data View to the layout editor.
3. Set the table's details using the Object and Hierarchy palettes.

4. Two subforms will be generated:

   • An outer subform that is the actual table
   • An inner subform that is the data row
5. The data row is generated like a regular form, but you can rearrange the position of the fields freely.
6. You can remove the fields that you do not want to include in the form table.

Creating the Booking Table – Cells

If you drag an internal table from the Data View to the layout, Adobe LiveCycle Designer creates one subform (the name of the subform becomes the name of the internal table), a second subform nested in the first one, and individual fields. This is due to the XML representation of the data.

If you want to create a nested table in this way, you have to repeat this procedure for the inner table.