Avaya Call Management System Custom Reports page 152

Advanced report design
!
Often, you need several "join" clauses in a Row Search criteria statement. For example,
you must first specify row search values for either the hagent or hsplit table if you
define a report field that contains the following data expression:
hagent.ACDCALLS/hsplit.ACDCALLS
You might enter the following "where" clauses:
hsplit.SPLIT = $i_split and hsplit.ROW_DATE = $i_date and hsplit.STARTTIME =
$i_time and hsplit.ACD = $acd
Note:
You must then specify join clauses so that the rows found in one table are related to the
values found in the other table. In the following example, you would add join clauses
(shown in bold) for every regular "where" clause:
hsplit.SPLIT = $i_split and hsplit.ROW_DATE = $i_date and hsplit.STARTTIME =
$i_time and hsplit.ACD = $acd and hsplit.SPLIT = hagent.SPLIT and
hsplit.ROW_DATE = hagent.ROW_DATE and hsplit.STARTTIME =
hagent.STARTTIME and hsplit.ACD = hagent.ACD
The report design shown in the figure below illustrates how this row search selection would
affect data in a report:
152 Avaya CMS Custom Reports
CAUTION:
If you run a report that merges data from two tables (particularly tables with
large amounts of data) into a single field and your Select rows where:
statement is not specific enough, you may get an error message when you
test the design. The specific cause may be that the number of selected rows
is very large, and CMS does not have enough space to create temporary
files. If this is the case, you should add additional "where" clauses to the row
search criteria.
Notice that table names are prepended to each database item.