Defining a File Location for a Custom Report

A custom report may require a file that needs to be loaded and rendered by a report viewer page. For example, all reports created using a Crystal Report have corresponding *.rpt file. If this is the case, the File Location field has to specify the file name and path.

Not all Custom Reports require physical report files. For example, if a Custom Report is created in ASP.NET or Business Objects, or if a proxy (intermediate) page is used, the File Location field must remain blank. A proxy page is a page that calls another web page on the same or a different server.

Defining a Relative File Location

If a Custom Report physical file is used and is located within the RAVE web application file tree structure,then a relative file location should be defined. A Relative file location indicates that the file is within the Rave application tree.

An example of a Standard Report’s file location-

~/Modules/Reporting/ReportFiles/PageStatus.rpt

An example of a Custom Report’s file location-

~/Modules/Reporting/Custom/Custom.rpt *

Note:Although Custom Reports may be stored in a location of your choice, it is strongly recommended that Custom Reports are saved in the Custom folder. Please create this folder if it does not exist.

Note:*Represents the root of the Rave web application. ASP.NET substitutes it at run-time with the actual physical location.

Defining a Full File Location

If a Custom Report physical file is used and is located outside the RAVE web application file tree structure, then the full path for the report file must be defined.

For example:

D:\OurCustomReports\CustomReport.rpt *

\\Server\NetworkShare\Folder\Subfolder\Report.rpt *

Note:*The account that the Rave web application is running under should have read access to the entered file location.