We are trying to run the Calculate ABC Codes report and are running into an error because the report .xml file is too large (300mb) preventing the report from generating. We do have over 400k parts which might be causing the issue. Is this a limitation with running on 32bit vs. 64bit? What is the cutoff file size limit running on 32bit and is this a known issue?
Anything over 200MB for the XML file is “large” by our standards, and generally at that point Support would recommend using the 64bit/64bit Crystal runtime to process that particular report. The size isn’t hard and fast as size is just one variable, but most customers that call in with a problem ~200MB seems to be the threshold.
In the past, upgrading to 64bit was not an option. Any other workarounds?
- Process the .XML with .RPT using the Crystal Developer.
- Generate a smaller dataset.
What does suggestion #1 actually doing? Does it reprocess the file using Crystal instead and will the format be the same as if running directly in Epicor vs. the Crystal Developer?
The runtime and developer have different rendering assemblies, and our experience is that when the .RPT is opened in developer with the dataset set to XML file that was generated from Epicor that it tends to process successfully when the runtime can’t.