When adding columns to a Report Designer report, fields from logically linked tables can be added to the same report, including custom elements created in the VIP - Data Dictionary. Between any two tables there can be two types of relationships:
- One-to-many: Created by joining tables.
- One-to-one: Created by joining fields.
Joining Tables
- After selecting one of the primary tables, hold your mouse pointer over it and then click
to join a table. The tables for selection here are tables that have multiple records for each of the rows in the primary table:
- Click
and select one of the following table joining methods:- Default: The main table record appears the same number of times as the corresponding secondary table records.
- Aggregate: The values from the secondary table will be concatenated within each of the secondary table columns. You can use this method to consolidate records.
Tips on Joining Tables
- Try to avoid joining one-to-many twice from the same source.
Example:- Start from Voyage > Voyage Itinerary.
- To know which cargo is loaded/discharged, adding Voyage > Cargo Handling directly results in too many lines. A better approach is Voyage > Voyage Itinerary > Cargo Handling.
If you have no choice but to join one-to-many more than once, plan each join carefully:
- Start with a plan for which columns you expect. If those are not available as columns in the Report Designer, you might have to export to an Excel output and then use a PivotTable for the result.
- If there is a logical link between the two tables added, there should be a logical filter to be applied, as in the example below.
Identify your primary table and the relationships you will use; make sure you have everything mapped.
Tutorial: Creating a One-to-Many Join
| Include Page | ||||
|---|---|---|---|---|
|
Joining Fields
The join icon, 
, indicates that a link can be made to another table via that field.
For example, you can click next to Ref Company No in the Cargo table to create a direct link to the Address Book table, in which that field is located.
On this Page
| Table of Contents | ||||
|---|---|---|---|---|
|