Reports

ActiveReports1 is a reporting tool embedded in Respond. Custom reports are created based on fields in the database. See Working with Reports in the ActiveReports online help to get started using ActiveReports.

PREREQUISITES:

  • A user must be assigned to the WORKMGR > Report Designer employee relate in order to access and create reports on the Reports page. See Assign Permissions to Employees in the Admin Guide for Trimble Unity Maintain and Trimble Unity Permit for more information
  • The first time you open Respond, you need to add any apps or pages you need or want to access. For example, use the Route menu option to add a menu item that navigates to the Asset Details, License Management tool, and other pages. See Add Menu Items and Edit Item Fields for more information. The Route is Report Designer for the new menu item.

When an active report is saved, it's automatically registered as an available print template for the corresponding activity type. Reports can be selected in Admin on the Work Activity Templates, the Preferences, and the Case Templates pages. Reports saved within ActiveReports can be found in the website directory under ...\<site_name>\cw-site-data\_tenant-data\_default-volume\tenant-1\reports. See Configure Printing for Service Requests, Configure Printing for Work Orders, Configure Printing for Inspections, and Configure Printing for Case Templates in the Admin Guide for Trimble Unity Maintain and Trimble Unity Permit for more information.

ActiveReports templates for work orders, service requests, and inspections can be uploaded in Admin using the Report Manager page. See Report Manager in the Admin Guide for Trimble Unity Maintain and Trimble Unity Permit for more information. ActiveReports templates for cases can be uploaded using the Systems Reports page. See Add a Report in the Admin Guide for Trimble Unity Maintain and Trimble Unity Permit for more information.

IMPORTANT: If a second connection string is used for ActiveReports and the database user isn't azteca, the user needs to be granted an execute permission for the DefaultMQADataSet stored procedure. For example, in SQL it would look like: "grant execute on azteca.DefaultMQADataSet to <databaseuser UID>."