Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
chriswain2
Creator
Creator

NPrinting image quality

I have created an NPrinting PowerPoint report. When I schedule the task and the server runs it, the picture quality is very bad. If I run the task manually in the designer immediately after, the picture quality is perfect. I attach two charts copied from the PowerPoint output to show the difference. Does anyone know the cause of this please?

1 Solution

Accepted Solutions
chriswain2
Creator
Creator
Author

Hi everyone, I have fixed the problem and can replicate it by reversing the fix. You had me looking in the right area, but it the clipboard zoom had no effect. What fixed it was ticking the following box:

In settings > user preferences > export > Under “Copying to clipboard” and  “Include caption and border” you need to tick the box for chart.

  

The strange thing is that the designer is using the same QlikView desktop but can work fine without this ticked. The designer must effectively tick this box when it runs but the server does not. That is what was most confusing.

 

View solution in original post

18 Replies
Colin-Albert

What version of NPrinting are you using?

v16 SR4 has some fixes to improve image quality, the extract below is from the release notes, I'm not sure if this change affects PowerPoint output.

JPEG quality improved in Pdf reports from Office templates

Office reports with JPEG images in the template produced pdfs with low quality images due to a compression during the generation process.

Not applicable

Chris,

One of the things you can do is to increase the image quality in the chart object attributes in the QVW.

Mike Czerwonky can give you more details on how to do this.

Best

Aran

Colin-Albert

I think this is the post Aran is referring to...

Improving Image Quality Export using Clipboard Zoom

chriswain2
Creator
Creator
Author

Hi Colin / Aran,

Sorry, you have missed the problem I have. The same NPrinting PowerPoint report gives different quality outputs when run by the server and by the designer modules. Why would this be the case? Everything else is the same. I am running version 16 on both modules.

I have just tested it by using the scheduler in the designer module which works fine and then set the schedule and run it via the server and it comes out poor quality again. Nothing else has changed.

It is not just poor quality resolution either. I am also getting cell borders appearing in tables where they do not exist in the qvw.

Thanks,

Chris

Daniel_Jenkins
Specialist III
Specialist III

Hi Chris,

Here's a shot in the dark - could you check for differences in the QlikView Desktop Settings > User Preferences > Export tab on the machine you run Designer and the one you run Server on? Log into the NPrinting server with the NPrinting server service account credentials when checking. If there are differences and if you match them up do you get consistent results?

I'm also curious to know the version of Windows that your NPrinting server runs on.

Let us know.

Daniel.

chriswain2
Creator
Creator
Author

Hi Daniel,

The server is on Windows 7. I am running the designer and the server directly on the server using remote desktop and I am logged on as the nprinting user and still get different results. They must be using the same desktop version.

Chris

Daniel_Jenkins
Specialist III
Specialist III

Hi Chris,

And what version of NPrinting do you use? Are Designer & Server the same version? If not on it already, could you upgrade to NPrinting 16.4 and try?

If you still have issues I suggest you open a case with Qlik Tech. Support.

Best,

Daniel.

chriswain2
Creator
Creator
Author

Hi Daniel,

It is version 16.3.

Thanks for your help - I will do that.

Regards,

Chris

Anonymous
Not applicable

Chris,

We are getting ready to update to 16.4 as well.  Can you please jump back on here and post if this solved your problem.  I see a number of fixes in the 16.4 release notes that likely would help us.   We are going to 17.1 when it becomes available this summer.

Mike