An issue has recently been discovered that involves Crystal Reports in Sage100 ERP version 2013. The issue relates to situations where a user attempts to print or export custom reports that contain parameters and have been included in the Launcher Custom Reports menu. When attempting to print or export/save such reports, users reported that the parameter window does not pop-up, and that they receive a “file not found” message (report not found).
The interim solution is to preview your Crystal Reports before printing, exporting or saving. Sage posted the following response to the issue in a Sage Community blog last week.
Reports that are previewed do display the parameter input window and function properly. We’ve tracked the issue to the SAP .net SDK utilized for Crystal Runtime development in Sage 100 2013. We are determining if we will have to write/implement this functionality ourselves or if we can have the SDK updated to include the functionality.
We will keep an eye on this issue and keep you posted of any updates or other resolutions. If you have any support related questions for any recent version of Sage 100 ERP (MAS 90), you may contact us.