This is an historic article, if you have not just upgraded from version 6 to the latest version of versaSRS this information is not relevant to you. This article contains up to date Custom Stored Procedures files.
When upgrading to versaSRS version 7 from version 6 the Custom Stored procedures are not updated as these can contain customisations that should not be overwritten.
For version 7 to be compatible with the Custom Stored Procedures then the following changes are required:
1. Access the versaSRS database under Programmability >> Stored Procedures, locate and take a copy of any Custom Stored Procedures that have been modified from the original. These include:
- sp_Get_Custom_Actions_By_Page
- sp_Get_Custom_Calls_By_Page
- sp_Get_Custom_ChangeRequests_By_Page
- sp_Get_Custom_Problems_By_Page
- sp_Get_Custom_Contacts_By_Page
- sp_Get_Custom_ManagedOrganizations_By_Page
- sp_Get_Custom_Dashboard_Call_Count_Summary
- sp_Get_Custom_Dashboard_ChangeRequest_Count_Summary
- sp_Get_Custom_Dashboard_Problem_Count_Summary
- sp_Get_Custom_Dashboard_Task_Count_Summary
2. The necessary scripts will need to be downloaded and run on the versaSRS database to make the necessary changes to these Custom Stored Procedures so that they are compatible with version 7.
NOTE: This will delete and recreate the Custom Stored Procedures, which is why the existing ones that have been modified need to be saved first. VersaDev takes no responsibility for any data corruption or loss incurred, be sure to take extra care not to remove or change any data by mistake when running queries directly on the database, we recommend performing a backup and implementing on a test environment before performing on production.
3. After running the scripts, apply any of the custom modifications made in the copied Custom Stored Procedures to the newly created Custom Stored Procedures.
Once the above steps have been completed then the Custom Stored Procedures will be compatible with versaSRS version 7 upon upgrading from version 6.