We're happy to see the new Print-to-PDF option implemented but we've got 1 form that doesn't want to print, giving an "Internal server error" message. Despite removing the form javascript that related to images we still haven't got it to work. Has anyone else come across things that are valid in the displayed form, but cause an issue with PDF generation? Possibly validation javascript, CSS formatting, fields/text hidden or displayed depending on Rule conditions?
Answer
Print to PDF - anything to avoid?
+5Best answer by gerardh
We have since found the cause: CSS includes used for formatting on the rest of our Sharepoint site were added within the Custom CSS section of the form. Removing there (as per advice of Nintex Support) fixed the problem for the moment.
From the documentation, I only documented unsupported features are the Page Viewer control and the Rich Text feature in the Multiple Line Textbox control is only supported in view mode. Other than that, the use of JavaScript shouldn't prevent a print, but what ever the script is doing may not be represented on the printed page.
Your issue could also be browser related, have you tried in another browser?
+5We have since found the cause: CSS includes used for formatting on the rest of our Sharepoint site were added within the Custom CSS section of the form. Removing there (as per advice of Nintex Support) fixed the problem for the moment.
That's great that it was resolved. And yes, we have seen in some related posts that some JS or CSS can affect how Print to PDF functions. Feel free to mark your answer correct so others can learn from your experience. Thank you for posting back
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.