As a general guideline, a positive tone likely will inspire more people to help you. Aran was merely pointing out that version consistency between Server and Client is necessary.
I can't tell from reading your post how you are creating your reports. Do you have a server or just use a client for the report distribution?
Here are some steps I might take to isolate your problem.
Can you rebuild the report and see if it fails, thus eliminating a potential compatibility issue from creation to production between versions?
Since you are printing a whole sheet object to a PDF document, can you just choose an image rather than the table when placing your object on your report?
Since your output is PDF, have your tried any of the other templates for building your reports rather than Word?
Perhaps you could post some screen shots with your failed output.
I have version 16 so unfortunately I have no way of testing your situation.
Hope that moves you forward.
Granted my comment wasn’t positive but accurately portrays my rough character and impatience with indirect problem solving. In the future I’ll just restrain myself further by not commenting.
To answer your questions:
I have 3 environments each of which demonstrate the same page truncation:
- Development Designer which is a playpen and has been upgraded to test different versions.
I rebuilt the report in my Development Designer environment and did not note that in my description… so this doesn’t work. I can however try rebuilding using other sheet objects from other non-sensitive reports and post the results.
Also, I did not note how I built the NSQ. I am using and image of the sheet and resizing the image so that it fits to the A4 sheet. I tried building an entity report which gives me the option of printing image files. I printed a PNG file which also printed a truncated view of the sheet.
What prints is if you look a browser view of report in full screen mode and you “Restore Down” so that you see a windowed 1/4 size window view. What prints is only the top left portion of a windowed view.
I find it difficult to believe I am would be the only one that prints this way and has this same experience.
I can understand the screen dump to a PDF. Have you just tried exporting a few of the charts directly rather than the whole sheet to your report?
Here is a screen shot of my export tab on my User Preferences screen. Do you have some of these boxes checked that might be affecting your outcome? When copying to Clipboard, if you don't have these boxes checked, I have seen it cause peculiar output. Of course, none of these boxes relates to a whole screen dump. Just something more for you to review. I have seen issues with scaling of exported images. Perhaps something was introduced with the QV version upgrade. I am still using SR9 of ver 11.
I use clipboard zoom to improve quality of the output, but this also forces you to do a one time re-size of each object you place in your report. I have not tried this with whole sheet images, however.
Have a look at this and let me know what you find. If you can upload a screen shot of a non sensitive example, that would likely be helpful too.
Working this problem in another direction, since my manual workaround does work; I’ll try and make permanent the windows “window” open maximize operation. This was also noted in the prior release notes:
---- Excerpt from prior notes, https://community.qlik.com/docs/DOC-13937: ----
- QlikView application window maximized when exporting an entire sheet as image
QlikView application window maximized when exporting an entire sheet as image
The QlikView application window is now maximized before exporting a sheet in image format. This means that the sheet image size depends on the size of the screen you are using. This also means that the image size exported from NPrinting Service may be different in terms also of resolution compared to the same sheets exported via the NPrinting application. This happens because NPrinting Service uses size and resolution defined in server Session 0.
As you pointed out that Nprinitng 126.96.36.199 actually fixed the problem with Qlikview at least to version 11.20 SR7, which you use. Then I think the later version of Qlikview (11.20 SR12, and SR13) breaks the fix. I encountered similar case before. And now maybe the latest version of Nprinting 17 and Qlikview 12 (not 12 SR1, there are still join bugs as I know) have already fixed the problem. Have you tried them?
If it is not, I think it is better you contact support team to let them know the new bug.