Contents|Index|Previous|Next

Customizing the Call Accounting, Coin, and Trouble Reports

The Call Accounting, Coin, and Trouble Reports all use whatís called a pre-query in order to perform the calculations necessary to produce the numbers in each report. The pre-query scans existing database tables for raw data, performs calculations on that data, then places the results of those calculations into a new table in the Windows temp directory. The report generator then accesses this new table to create the report. When Panorama is shut down, the temporary table is erased.

The pre-query routine is designed to handle changes to the items in the bottom half of the Reports window. However, if changes are made to the report itself by changing such things as the layout, the SQL code, or the database table fields used, the report generator automatically changes the report type to User Defined. This change in type will make the report not go through the pre-query routine; the temporary table will not be generated, and a message will state, ìNo Recordsî when the report is ran.

It is still possible to produce a customized Call Accounting, Coin, or Trouble report, though:

1. Create the report, making all necessary changes within the Edit, View, and Print Reports window, but without making the above mentioned alterations that cause the report to become User Defined.

2. Click Save.

3. Clone the record, giving the clone a name that will indicate that it will be a customized version of a standard report. Hint: Reports are displayed in alphabetical order, by the Report ID. The standard coin report might be called ìCoin,î while the customized version might be called ìCoin 2,î thus making one immediately follow the other in the list.

4. With the clone report selected (Coin 2), click the Edit button in the Edit, View, and Print Reports window, then click Select.

5. Make any desired changes in the resulting window, including layout, SQL code, and database fields used.

6. Click Save. Close the window. Notice the clone is now typed as User Defined.

7. Run the standard report for the custom report desired. This will cause Panorama to run the pre-query routine and create the temporary table.

8. Now run the custom report that is a clone of the standard report. The report generator will access the table that the standard report generated and place the information in the custom report.

When Panorama is shut down, the temporary table will be erased, so each time Panorama is started up, the standard report must be run again before the custom report can be successfully run. Also, if changes to the information have occurred, as when phones have been polled and new information is present, run the standard report before running the custom report, or the new information will not be present.

If a new date range is desired, or any changes are made to the standard report, a new clone of the report must be made, along with the changes that made the clone a custom report.