Unable to change the NPrinting connection when importing a PowerPoint report

[hudhud_hoda]

Hello everyone,

I’m encountering a behavior in Qlik NPrinting that I don’t fully understand, and I’d like to know whether it is expected or if I’m missing something.

Here is the situation

I export a report from N Printing

Then I import it into another Nprinting App with another connection

it is well working with Excel reports, I am able to change the App and assign a new Connection without any issue

However: with power point, NPrinting does not allow me to change the connection when importing the report.

For context:

I duplicated the original Qlik Sense application, created a new NPrinting App and Connection, and attempted to reuse the same PowerPoint report template — but NPrinting prevents changing the connection during import.

Is this a normal limitation for PowerPoint reports in NPrinting?

And if so, is there any recommended workaround to reuse PowerPoint templates across different N Printing Apps/Connections?

Any insights or explanations would be greatly appreciated.

[rubenmarin · Accepted solution]

Hi, if it helps, when I found that a connection was selectable when importing the report, it was becasue something was missing in the app related to the new connection.

I would double-check that all the objects used by the report exists in the new app, and confirm than the report only uses objects from that connection. The NPrinting logs can give some hints on what objects were not found.

You can also create a connection to the same app that uses the other connection to confirm if it works with that connection.

[Lech_Miszkiewicz · Accepted solution]

Hi @hudhud_hoda 

There could be few reasons why this is happening but as @rubenmarin suggested it will be caused by the fact that you are trying to connect to app which does not have all objects used in original report.

It goes down to good practices as you could have following issues: 

• It is possible that you have built that report based on user / community sheets objects and when duplicating app those are not duplicated. It is obvious but often overlooked. The gold rule should be that you only work with the base sheets and NPrinting should never use public/community sheets.
• Changes to data model -  it is possible that there were changes done to data model which could in theory affect components used in the report. That can include things like filters which point to fields removed from the report. Such scenario may not cause issues in old report but it will prevent you from recreating new one
• section access - object visibility - just make sure your new app is published to stream which has the same privileges as well as app connection is used with the same user.

Cheers

Lech

[hudhud_hoda]

thanks alot

i have done what @rubenmarin  and it works 

i had some graphs were missing in the new connexion Nprinting