Creating PDF of Order Confirmation: PDF is blank? (12 replies)
- What version of Sage and IMan?
- Not sure what parameters are you setting?
- Sage v2019. IMAN Version:
Assembly Versions:
Realisable.IManWebUI.DLL 4.1.0.0 Product Update: PU4
Config Version: 4.11
DB Version: 4.13
2. Parameter - I'm passing through Order Number and setting " include confirmations already printed" to true- here's the map, trying to replicate what I see in O/E Forms.
Link to image as it doesn't seem to allow me to upload the .png
Howdy all,
I found the answer to issue #2 - I was mapping "Include Confirmations Already Printed" as "True" when it needed to be "1." So that solves that.
So, any suggestions on the error I am seeing with issue #1?
Accpac Print Error Crystal Reports Error: The type initializer for 'a4wcrInterop.ParameterDialogConstant' threw an exception. Error while exporting report to file.
What is the path of the file you're trying to export to? Including extension?
The file should be of .pdf or .rtf extension.
Trying to export to : "E:\_Temp\" & %PARENTORDR & ".pdf"
This works fine with the basic OECONF01.rpt form, but throws that error when I use this other custom form.
Hi there,
Just an update- still needing some advice please. We've made some adjustments and can print the custom order form through the Sage 300 O/E Forms UI but still cannot create the PDF using IMAN. I've restarted services & cleared the cache.
Still getting this error when trying to create the PDF:
Arline, if the basic confirmation is working, but the customised form is not, then there is something in your customised form which is the problem.
What specifically do you mean by 'We've made some adjustments and can print the custom order form through the Sage 300 O/E Forms UI but still cannot create the PDF using IMAN'? Do you mean the form at some point wasn't working and now it is? Perhaps that might identify the issue?
How specifically is your form customised? Does it ask for custom parameters? If so, then you're out of luck, we do not support that.
So we added an .ini file to the directory in which the custom form resides, and that allowed us to print through the Sage O/E Forms UI with no issues. If you're interested, the .ini file's contents are:
https://www.dropbox.com/s/h9jx3w4j9j3ovrh/oerpt.ini?dl=0
That made the difference in the form NOT working through the Sage UI and working in the Sage UI. But that change did not affect my ability to print it through IMAN. The form asks for the ORDNUMBER parameter and no custom parameters. I understand how IMAN would not support custom parameters, makes sense in this use case. I just don't understand why, if we added the .ini file and it started working through the Sage UI, why it will not work through IMAN?
Do you have customisation directories setup?
Any suggestions on what I might need to fix here?
I am trying to create a PDF of an order confirmation and I've encountered issues with 2 different forms. Hoping you can advise me?
Route 1: custom form: Ideally: I'd go this route: I use the Order Confirmation Print dialog in the Sage 300 connector. I use the "Order Form" map transform to point to the specific Crystal Report I want. When I do that, I get this error consistently:
Accpac Print Error Crystal Reports Error: The type initializer for 'a4wcrInterop.ParameterDialogConstant' threw an exception. Error while exporting report to file.
Can you help me understand this? From what I've read online it seems like there's a Crystal dll that needs to be registered on the machine but I'm not sure.
Route 2: Basic OE Conf Form: Just as a test, I tried to print the regular Order Confirmation Form. In the "Order Form" Map I tried both of these things and they both printed a totally blank PDF.
Tried: OECONF01.rpt
Tried: E:\Sage\Sage300\Programs\OE66A\ENG\OECONF01.rpt
I can easily print this form through the Sage 300 O/E Forms dialog. Why is it producing a blank PDF?
Thanks for any advice.