Versions Compared

Version Old Version 4 New Version Current
Changes made by

Documentation Reviewer

Documentation Reviewer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To find a complete list of system requirements across all the Signature modules, refer to the Signature System Requirements document found on the Product Download page on Signature Resources. https://portal.key2act.com/customer-portal/downloads

Prerequisities

Certain IIS features must be installed before you can enable SQL Server Reporting Services to be installed with SQL Server. For SQL Server 2012 or later, select all the System the System Requirements, as well as the additional features below. Select Start > Administrative Tools > Server Manager > Roles > Add Roles, and select the Web Server (IIS)role to configure.

...

For Equipment Management, you must also set up your SSRS reports in the Report Definition Setup window (Microsoft Dynamics GP > Tools > Setup > Equipment > System > Report Definitions). For step-by-step instructions, refer to the Advanced Rental feature chapter of the Equipment Management User Guide.

Step 2: Set up the Company Logo (

...

Optional)

You can customize the company logo that appears on some of your customer-facing reports, for example, invoices.
For each of the reports that display a logo, the .rdl file points to the subfolder Signature Images and the file Company Logo. The default logo is a transparent image that appears on the reports as blank.

If you want your own company logo to appear on the reports, you can replace this image; however, DO NOT delete the default logo unless you are replacing it. If the .rdl cannot locate Signature Images\Company Logo, the logo appears on the report as a missing image.

...

  1. In Report Manager, locate the company where reports are deployed, and open the folder Signature Images.
  2. Rename or delete the default Company Logo file by choosing Show Details, then Edit or Delete.
  3. Return to the Signature Images folder and select Upload File. Before uploading, change the name of your new logo to Company Logo (no file extension), then select OK.
       


Step 3: Set up Signature

...

SSRS Reports to Print from GP

To set up Signature SSRS reports to print from the appropriate window in the GP application, you must replace the provided Dexterity reports with the corresponding Signature SSRS reports. This requires that you either manually populate the WSRepts table with the pathname to the replacement report, or run the stored procedure WS_SetReplacementReportsForSRS, which populates all applicable Signature SSRS report pathnames into the table.

Info

About the WSRepts

table

Table

The table WSRepts stores the path location for replacement reports. This table is created in each company database during the Signature installation or upgrade process.

A select statement on this table yields something like the following:

The ReportReference column identifies the name of the report you want to replace, most likely a Dexterity report name.

The ReportLocation column stores the full path and file name of the report being referenced. This could be a local SSRS report or the URL of a remote SRS report. A blank column assumes the system is running the Dexterity version of the report. To replace the Dexterity report with the SSRS report, you must populate this column with the SSRS report location.

In the example below, an existing Dexterity report is replaced with an SSRS report using the stored procedures.

UPDATE WSRepts Set ReportLocation = 'http://localhost/ReportServerNew/TWO/Signature Service/Service Cost Audit' where ReportReference ='SV_Service_Cost_Audit_Report'
If you are replacing reports individually, you can determine the name of the Dexterity report by printing that report from within the Signature system. For SSRS reports, you also need to know the machine name on which your report server resides.

Running the SQL Stored Procedure

The SQL procedure WS_SetReplacementReportsForSRS globally replaces all applicable Dexterity reports with the SSRS report equivalent.
Running this procedure DOES NOT update a ReportLocation that already contains a value; it only applies to blank ReportLocation columns, which assumes that the Dexterity report is being used. If you already have a custom report specified to replace the Dexterity report, it will not be overwritten.

To replace Dexterity reports, run the following command against the company database to call on the stored procedure: exec WS_SetReplacementReportsForSRS
The common printing DLL Signature.ReportControl.dll provides the WSRepts table and the two SQL procedures that can be used to set up SQL reporting. For more information on this DLL, refer to the user manual.

...