Custom Reports

Lucity has its own set of Crystal Reports stored on the web server. Often agencies would like to customize these reports and add their own reports. Any custom desktop reports need to be converted to Web use. The following sections provide information about how to implement custom reports.

Naming Reports

Users should not edit the reports provided by Lucity. These are updated with every upgrade and therefore all changes will be lost when the agency upgrades. Instead, users should either make a copy of an existing report and give it a new name or they should create new reports with unique names that do not conflict with the standard reports.

Report Location

Custom reports must to be copied to the web server. All reports must be added to the /Lucity Web/Reports folder. However, the .rpt files can either be placed in the built in folders (/Reports/Equip, /Reports/Work, etc...) or they can be placed in a custom folder (/Reports/PublicWorks, /Reports/Work/Custom, etc...). Wherever they are placed they can be pointed to when adding the report to the Report Manager.

Creating Custom Reports

Training Manuals - Every ACT there are several sessions and training manuals dedicated to creating Custom Reports.

Converting Desktop Reports - If an agency has a custom report they use in Lucity Desktop they must follow these directions before adding it to the web.

SQL Server Data Provider - When using SQL Server, custom reports must be connected to the data using these instructions.

Oracle Server Data Provider - When using Oracle, custom reports must be connected to the data using these instructions.

Report Parameters - Some requirements and special parameters available for Lucity Web.

In This Section

Converting Desktop Reports

SQL Server: OLE DB (ADO) Data Provider

Oracle: Oracle Server Data Provider

Report Parameters

See Also

Reports

Available Modules