Using Join Conditions
You can override join types at design time, for example, you can define a report that includes all account codes where there are no transactions in the selected period range.
Example
When you select the account association to be Right Outer in a ledger line-to-account association, the expected output is as follows.
The header line is printed for all accounts, whether there are transaction lines in the selected period or not.
Account | Period 2 Opening Balance | Period 2 Movement | Closing Balance O/B Period 3 |
---|---|---|---|
11000 | -13,234.23 | -1,000.00 | -14,234.23 |
12000 | -10,000.00 | 0.00 | -10,000.00 |
13000 | -12,234.19 | -1,600.00 | -13,834.19 |
Although there are no rows for account 12000 in Period 2, the sum of the period movement values is zero (0.00) and not null.
When you select the account association to be an Inner Join in a ledger line-to-account association, the expected output is as follows:
The header line is only printed for all accounts, where there are transaction lines in the selected period.
Account | Period 2 Opening Balance | Period 2 Movement | Closing Balance O/B Period 3 |
---|---|---|---|
11000 | -13,234.23 | -1,000.00 | -14,234.23 |
13000 | -12,234.19 | -1,600.00 | -13,834.19 |