Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Reports

All reporting is done via Crystal Reports

Reports and Slots

Crystal Reports

This details conventions and requirements for developing Crystal Reports.

Crystal Reports Runtime v13 is being used on the Appliances themselves. Report development is being done in v14 on Stella.

Database Connections in Crystal

There are two ODBC connections available:

  1. The main database (WOL_Prod)
  2. The logs and stats database (WOL_Prod_Log)

ODBC connections are configurable in Site Settings. But generally shouldn't need to be changed from their default in production environments.

Reports themselves have their connections remapped to the config settings. The convention is as follows:

  1. Any DSNs which do not start with WOL_ are not touched
  2. Any DSNs which start with WOL_ and end in _LOG are remapped to the logs and stats database
  3. Any DSNs which start with WOL_ and do not end in _LOG are remapped to the main database

Parameters

The following common parameters are passed to every report:

Crystal NameData TypeSample ValueComments
__ApplianceRootUrlstringhttps://demo.wiseowllegal.com.auUsed to load a custom logo: combine with "/CustomReportLogo"
__CurrentUserstringlarry.lawyerThe current user name who is running the report
__ReportNamestringTrust Trial BalanceThe name of the report as listed in the reports in Wise Owl Legal. Note that this may be different from the Crystal Report name. 
__ReportIdinteger8The report id which is being run. You can access additional information about the report via the table report.CrystalReport. 

Other parameters are passed based on view model data, ONLY when the report is assigned a to slot and the user clicks on the Print icon, base on the following rules:

  • Any readable property of the view model is mapped to a corresponding Crystal Parameter based on name.
  • The Crystal Parameter may be prefixed with a "p". That is the view model property "MatterNumber" can be mapped to either "MatterNumber" or "pMatterNumber" on the Crystal Report
  • Mapping is case-insensitive.

The actual values in view model data varies from page to page, however the following pointers should help you find the right parameters:

  • Most pages which show a single record will have an IDproperty which relates to the primary key of a database table.
    • Trust Transaction Lines, however, have a composite primary key based on the transaction id and line number.
  • Pages which allow searching of records commonly have a Name property.
  • You can view the raw view model data by appending ?__ViewModelDebug=y to a page you load. This will show all the view model properties available; usually there will be enough there to pass to a report.

Any report parameters not mapped by Wise Owl will be shown on the usual Crystal Reports parameter dialog. This allows for a last ditch attempt to map parameters, but is generally not the best experience for the user.

Any reports viewed directly from the report list will rely on the Crystal Reports parameters dialog.

  • No labels