Integrating Crystal Reports with SIGNZ (V3.59, July 2008) Integrating Crystal Reports with SIGNZ (V3.59, July 2008)

SIGNZ can have reports created by Crystal Reports (and saved as RPT files) integrated in the SIGNZ Reports screen as well as the Reports tab in the Contracts screen and SIGNZ-based web sites.

The first step is to design the report in Crystal or (as shown here) in Visual Studio. We’ll create a Standard Report The first step is to design the report in Crystal or (as shown here) in Visual Studio. We’ll create a Standard Report

Create a new OLE DB connection for SQL Server

Enter server connection details. Design against your training database – SIGNZ will replace the connection details here when the report is run with the correct database.

Here you have the choice of Add Command if we have given you a SQL statement to execute OR you can click + on the database and select from a view or tables as appropriate.

Here we create a command and create a parameter. In this case we are creating a report to show bookings for just one ContractID. Create the Parameter and then double-click to add to the query. SIGNZ will fill this parameter with a valid Contract ID (if this report is run from the SIGNZ contracts screen). SIGNZ support staff will advise the query and / or Parameters that may be relevant for the report you are writing. Here we create a command and create a parameter. In this case we are creating a report to show bookings for just one ContractID. Create the Parameter and then double-click to add to the query. SIGNZ will fill this parameter with a valid Contract ID (if this report is run from the SIGNZ contracts screen). SIGNZ support staff will advise the query and / or Parameters that may be relevant for the report you are writing.

Because we have created a Parameter report we need to add a valid ContractID here to proceed with designing the report.

Add some fields and … possibly some Grouping and Sorting and Finish.

One report … ready to customise. The report should normally be saved (or copied) to the Reports folder under SIGNZ program files. See CrystalPath in SIGNZ.INI for alternate locations. One report … ready to customise. The report should normally be saved (or copied) to the Reports folder under SIGNZ program files. See CrystalPath in SIGNZ.INI for alternate locations.

Now it’s time to link the report into SIGNZ …

Report title that will appear in reports screen … The icon you would like (otherwise you just get a ‘printer’. Icons are under SIGNZ \icons folder. A more detailed description if you want one. This appears to the right of reports screen when this icon is clicked.

The group of reports (sites, contracts, owners, installations) you would like this to appear under. The RPT file for this report. This should be a shared folder on the server, preferably the reports folder under SIGNZ. See SIGNZ.INI CrystalPath entry fior an alternate location.

Where does the report get viewed. Currently valid entries are: - Web – visible via Reports in SIGNZ web sites - Reports – Reports screen in SIGNZ - Contracts – Reports tab of the Contracts screen As we created this report with a ContractID parameter I only want this visible from Contracts … and SIGNZ will supply the current ContractID to the report. Where does the report get viewed. Currently valid entries are: - Web – visible via Reports in SIGNZ web sites - Reports – Reports screen in SIGNZ - Contracts – Reports tab of the Contracts screen As we created this report with a ContractID parameter I only want this visible from Contracts … and SIGNZ will supply the current ContractID to the report.

If your report contains other Parameters then they would be listed here and you can give them a value for this report. For example, you may design a report for Installations and then add a parameter for ‘state’. You could then add the same RPT in here many times (one for each state) and use this screen to filter the report. That way you could have: -Installations NSW -Installations QLD -Etc -In your Reports screen. If your report contains other Parameters then they would be listed here and you can give them a value for this report. For example, you may design a report for Installations and then add a parameter for ‘state’. You could then add the same RPT in here many times (one for each state) and use this screen to filter the report. That way you could have: -Installations NSW -Installations QLD -Etc -In your Reports screen.

There is one additional field we need to add here – SECURITY. The security field allows you to decide WHO sees this report in SIGNZ. If you typed ‘InstallationsMobile’ in that field then ONLY people that have been granted the ‘InstallationsMobile’ permission in the SIGNZ Security program will see that entry. There is one additional field we need to add here – SECURITY. The security field allows you to decide WHO sees this report in SIGNZ. If you typed ‘InstallationsMobile’ in that field then ONLY people that have been granted the ‘InstallationsMobile’ permission in the SIGNZ Security program will see that entry.

Your new Security entry would appear * here and you can double-click the cells to decide which groups of users can see the report. By default SIGNZ admin users (those in blue under Staff) see all reports. Your new Security entry would appear * here and you can double-click the cells to decide which groups of users can see the report. By default SIGNZ admin users (those in blue under Staff) see all reports. Note: it won’t ‘appear’ until the first non-admin user loads the reports screen after your new report is linked in!

Ta-da … ! You may need to exit SIGNZ to see this if you have previously loaded the Reports data into memory. Ta-da … ! You may need to exit SIGNZ to see this if you have previously loaded the Reports data into memory.