Using Explorer, review the contents of the DYNAMICSSL\USR_RPTS directory and determine if *.RPT file noted in Step 3 is found there. Determine if the report is a Standard Dynamics SL report.Ī. Note all information, as it will be required in later steps.Ĥ.
Based on the example, the Standard format of the Detail General Ledger report is stored in ReportFormat00 and the corresponding *.RPT Report Filename - 01620 - is found in ReportName00. This is the *.RPT filename used by Dynamics SL when printing the report. The corresponding Report Filename will be found in the matching ReportNameXX field. Locate the desired Report Format name and note which ReportFormatXX field it is found in. Review the information stored in the ReportFormat00 - ReportFormat07 fields. For this example 01620 is representative of the GL Detail General Ledger Report (01.620.00)). The value should be entered in quotes and without the decimal. (where theReportNbr = the first 5 digits of the Report screen. SELECT * from RPTCONTROL where ReportNbr = '01620' To do so, access the appropriate System database and execute the following statement: Using Query Analyzer, determine the Report Filename corresponding to the Report Format, noted in Step 2.
For example, if troubleshooting the General Ledger Detail Report determine which of the two Report Formats is being used: Standard or Multi-Currency.ģ. Determine which Report Format is selected when printing the report. Determine which report is being printed by reviewing the Report Name and Screen Number which appears in the title bar of the ROI screen.Ģ. Note - If any questions arise during the troubleshooting process, contact Technical Support for clarification prior to attempting the recommended action.ġ.
Resolution 13127 - Troubleshoot a Crystal Report® used by Dynamics SL. For complete instructions on troubleshooting a Crystal Report®, see resolution 13127. If however, the error seems to be specific to only that database, then it may be an indication of a problem with the actual data rather than an application error.Ĥ. If the same error can be recreated in other databases (Demo databases), Dynamics SL Technical Support will then document and submit the test steps to a Dynamics SL Development group so that a correction may be delivered. The next step is to determine if the problem is related to the database or the application by trying to recreate the error. Has this report ever worked? What changed?ĭoes the report work in other databases (i.e. What format of that report is being printed?Īre a template, sort, and/or a select being used? In order to do so the following questions should be asked to help understand the details of the problem: The primary objective of the Report Troubleshooting process is to identify the cause of the reporting error. Microsoft Dynamics SL is not obligated to provide debugging support for modified or newly developed reports, but will follow normal Technical Support troubleshooting techniques(outlined below) to verify that no Microsoft Dynamics SL error exists.Ģ. Microsoft Dynamics SL provides support for the installation of Crystal Reports®, the contents of its standard reports, the performance of its standard reports and responses to general how-to questions regarding basic functionality within Crystal.
#Crystal reports runtime change max records how to
How To Troubleshoot Crystal Report Errorsġ. How To Troubleshoot Crystal Report® Errors
0 kommentar(er)
