Upgrade Version 4 Report Definitions
This tool upgrades any reports in the Reports Wand Administrator Template to meet the required syntax for Version 5.
This tool can be re-run after changes have been made to failed items only. Items that have been marked as successfully processed, or already upgraded, will be ignored on subsequent runs.
Renaming Reports
If the upgrade process completes successfully, or the report already meets the v5 syntax requirements, the report Short Name and Program Name are updated. By default the Short Name has “_V5″ appended, and the Program Name has ” v5″ appended. You can modify these names to meet your preferred naming standard before processing the reports to upload them to the Oracle server.
First, download all Report Definitions into a new Reports Wand Administrator Template. See how here.
Once all the reports have been downloaded, click the Upgrade button.
A dialog will appear explaining the process, and asking if you want to continue:
Click Yes to continue, or No to exit without upgrading any reports.
Each report will be processed, and the result of the upgrade process will be marked in Column B next to the report ID.
There are three possible outcomes:
- The report definition is processed and upgraded successfully. These are marked in Green. This report is ready to upload to Oracle.
- The report definition already meets the v5 syntax. These are marked in Orange. This report will have had it’s name and description changed.
- The report definition could not be upgraded. These are marked in Red.
There are two possible reasons that a report will be marked in Red, and not be updated.
- A bind variable named in the template could not be found in the SQL.
- A bind variable exists more than once in the SQL.
These reports that are marked in Red need to be manually fixed.
Fixing A bind variable named in the template could not be found in the SQL
To fix these errors, it is necessary to review the bind parameters in the SQL, and ensure they match the Param Name column (usually column J) exactly, including the case of the letters.
A v4 Bind Parameter in the SQL will be wrapped in square brackets, something like this:
[MY_PARAMETER]
If the name in column J is My_Parameter, then the search will fail.
Find any mismatched parameters, and update either the SQL or the parameter name in the template, and re-run the upgrade process to ensure the change has been made correctly.
Fixing A bind variable exists more than once in the SQL.
The SQL of these reports needs to be modified. Instructions on how to do this are here.