The fields tree shows the fields of a type or database entry point. It is used in the page designer and in the view editor. The fields tree is a slice of the schema, that is reachable from a certain entry point.

The fields tab is filled when a template or a view is edited.

FieldsTree

Each branch in the tree indicates a navigation step in the database that results from an object reference or join. To follow a link there is no need to specify joins or navigation explicitly. Just open a branch and drag the element onto the page. ReportWeaver will automatically generate the necessary access code.

  1. This is the data entry point.
  2. A collection (or 1:n) relationship. Dragging this onto the template creates a seetable.
  3. An object reference (1:1 relationship) within the collection object.
  4. A nested collection. This is the case if one collection appeas within another collection.

The icons indicate the the type of the field:

Indicates a literal string field.
Indicates a numeric field.
Indicates a boolean literal field.
Indicates an object typed field. I.e this appears when there is an object reference or 1:1 join in the data. If you put an object value into a cell of the template, then ReportWeaver will display the value of objects toString method.
This indicates an object typed field, that has been specified by a user defined view.
This indicates an object typed field, that is the result of a cast operation in the view.
This indicates a collection or 1:n join in the data. If you drag this onto the template, the seetable  wizard will pop up to create a table.

Note:  You can drag a field of a nested collection only into a table of the surrounding collection.

This indicates a map (dictionary/hashtable) in the data. A dictionary is displayed as a collection of key/value pairs.