A Join table is a combined table based on a relationship between two tables, for example
Event_ID. Join tables are defined by a join expression and can be recognized by the icon.
Follow these steps to create a join table.
Open your app in your development environment and go to the Data tab.
Right click in the left panel and select New table > Join table….
A new table has been added to your list of tables in the Data tab. The join table does not contain any table items as a join expression must be defined first.
Follow these steps to define a join expression.
Right click on the join table and select Edit….
Enter a join expression.
Click on OK.
See illustration below for an example.
After finalizing the join expression, the resulting items which are available in the table item list, are displayed in in the join table. The join table has two groups of items, which are the respective tables which are used for the join. See illustration below.
In a join table you can create expressions that use datasource attributes from both the original.
In the table item list, these expression are placed outside the original table groups. This means that the scope of the expression is on the join table and not on the individual tables. These groups help you as a developer to see in which table items are originally defined. See illustration below.
If you double click on an expression, the Edit Expression Attribute dialog opens.
On the right of the general section of this dialog, Table also displays where the expression attribute was originally defined.
To control in which tables a table item will be available, it is possible to set the following availability options.
- Public: The item is available in the current table, and in join tables using the current table.
- Private: The item is available in the current table, but not in join tables using the current table.
- Hidden: The item is not available at all.
See illustration below.
The availability of an attribute or control can be set per table. For example, if in the original table the datasource attribute is Public, in the join table the availability can be Private or Hidden.
If an item is not available in a certain table, then it cannot be used, for example, in expressions or charts.
Follow these steps to set the availability of a datasource attribute to Private.
Go to the Data tab.
Select the table that contains the attribute you want to set to Private.
Right click on attribute in the table item list and select Availability > Private.
The attribute is now displayed Italic and is greyed out, which means it is Private. See illustration below for an example.
Follow these steps to set the availability of a datasource attribute to Hidden.
Go to the Data tab.
Select the table that contains the attribute you want to set to Hidden.
Right click on attribute in the table item list and select Availability > Hidden.
The attribute is not visible anymore in the table item list.
Hiding a table item ensures the item cannot be used anymore. If the item was still referenced before hiding it, you will create so called “ghosts”. See Maintain Application Integrity.
Click on the menu in the table item list to enable the option Show hidden. This enables you to see table items which are set to Hidden in a table, and to change their availability. See illustration below.
The Show hidden setting is remembered per user and is not set per application.
Join tables can also filter data records by using the
where clause in the join expression. The where clause works the same as in SQL.
Invoices leftjoin Events on Invoices.Invoice_number = Events.Invoice_number where Country = 'UK'.
Immediately after applying the change to the join table, the Table Item Mappings dialog shows up to map the new table items. This is necessary as the new set of table items might be different than original one. See illustration below.
Under Branches, the used tables are shown, under Table Items, the items from these tables.
Follow these steps to inspect the mappings of the table items.
Click on next to each option in the Table Item Mappings panel.
Verify the mapping is correct and click on OK.
It is possible that all items were able to be mapped automatically. Depending on the change made to the join expression, some table items will not be mapped yet, and a decision must be made how to proceed. See illustration below for an example
Not all mappings were able to be automatically detected. In the Warning section at the top, the table items that do not have a correct mapping are listed.
Follow these steps to fix incorrect mappings.
- Map the tables in the Branches section as good as possible.
- Map multiple table items at once by mapping the paths marked with and shown in red in the Table Items section.
- Expand the paths which still have problems (use the next to the ) and try to map items one by one.
- For items that cannot be mapped, choose Ghost and resolve those manually afterwards
When the number of table items is small, you can start with step 3 as there are only a few mappings to correct anyway.
Updated 27 days ago
|Maintain Application Integrity|