Before Upgrading

Step 1: Verify version compatibility

Before upgrading, verify the Signature version you are currently running is compatible with the version you are upgrading to by referring to the Signature Readme file.

Step 2: Back up the Microsoft Dynamics GP databases on the server

Back up all Microsoft Dynamics GP and Signature server application and data files.

Step 3: Back up the client directory on a workstation

Back up all Microsoft Dynamics GP and Signature files on a workstation, including dictionary files for custom reports and windows.

1. When an upgrade is installed, the dictionary files containing the custom windows and reports are replaced.
2. A backup copy of the dictionary files is used to restore the customized windows and reports for Job Cost and Service Management applications after the upgrade is installed.

Step 4: Test a restore

Ensure that the copied application and data files are functional and could be used in the event of a failed upgrade.

Step 5: Commit all batches and records

If you have a batch with salary transactions that are only partially entered, do NOT commit the batch. Once you commit, you will not be able to enter the remaining salary transactions for that batch after upgrading.

1. In TimeTrack, commit all transaction batches. Committing all transactions before upgrading ensures that data will not be lost.Follow the procedures in the "Committing time card transactions" section of the TimeTrack User Manual. We recommend you print the WS Time Sheet Committed report during the commit process.
2. In Signature Utilities, commit all records in the Location Import Warehouse table. For instructions, see the Signature Utilities User Guide.

Step 6: Back up custom security settings

The default roles and tasks provided by Signature, which are marked with an asterisk, will be overwritten by the upgrade process. If you have made any modifications to these roles and tasks, those modifications will be lost after the upgrade.

To keep your modifications, we recommend making copies of and renaming any default roles and tasks that you have modified. After upgrading, you can update your security settings to include access to new windows and functionality, then adjust user-level security to include the copied roles, rather than the default roles.

Step 7: Print copies of modified windows and reports

Modified Signature and Microsoft Dynamics GP windows and reports may not convert properly to Signature 2018. Print copies of all modified windows and reports to use as a reference if you have to re-create them after you upgrade.

Step 8: Post transactions

To ensure all transaction data is written to Microsoft Dynamics GP before an upgrade is installed, post as many transactions as possible before upgrading.

• Post Service Management transactions. Refer to the "Service Invoicing Procedures" chapter in the Service Management User Manual for posting procedures.
• Post batches containing Job Cost transactions. Refer to the "Transactions" chapter of the Job Cost User Manual for posting procedures.
• If you are upgrading from a version prior to Signature 2013 R3, for data integrity, all service invoice batches need to be posted.

Call WennSoft Support if you need help posting transactions.

Step 9: Back up all Signature application and data files

Step 10: Remove existing Signature SSRS reports

SSRS reports are frequently updated and enhanced with each Signature release. To successfully replace the old reports, you must remove the existing Signature SSRS reports before you upgrade.

Delete Signature SSRS report files

1. Browse to the location where Microsoft Dynamics GP is installed, for example, C:\Program Files\Microsoft Dynamics\GP.
2. Open the Signature folder, then locate and delete the folder SRS Reports. When you install Signature 2018, this folder and all the Signature SSRS reports contained in this folder will be replaced by the new and enhanced reports.

Remove the deployed reports

1. In a Web browser, open the Report Manager for SQL Server Reporting Services. The location of the Report Manager is most likely http://MyMachine/MyReportServerName where MyMachine is your machine name and MyReportServerName is the name of the report server given when you installed SQL Reporting Services. To determine the name of the report server, choose Start > All Programs > Microsoft SQL 2012 > Configuration Tools > Reporting Services Configuration. Connect to your server and choose Report Manager URL. The Name field on this page contains the name of the report server.
2. In Report Manager, click on a company name to open the location of the reports for that company.

3. Delete any Signature SRS reports that have been deployed to this company. After upgrading, when you deploy SRS reports using the new deployment wizard, these reports will be replaced. 

   

   • Do not delete any reports that were not provided by Signature, as these reports will not be replaced by the Signature deployment wizard.
   • You can delete multiple reports at once by using the Show Details button to expose a checkbox next to each report name. Locate and mark the checkbox next to the Signature reports, then choose Delete.
   • By default, Signature reports are organized into folders by product. If you have kept this default organization, you can delete the entire folder for each Signature product. If, however, Signature reports have been rearranged into other folders that also contain non-Signature reports, do not delete the folder; rather, open the folder and individually delete only Signature reports.
4. Repeat steps 2-3 for any additional companies that use SSRS reports. Signature reports may have been deployed across multiple companies.

Step 11: Upgrade Microsoft Dynamics GP

See the Microsoft Dynamics GP Update Instructions. Be sure to open each company in Microsoft Dynamics GP and make sure it is functioning before upgrading Signature products.
Refer to the SignatureReadme file for up-to-date version and service pack requirements.