Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
i built a pixel perfect report using NP 16 and QlikSense. We have since upgraded to NP 17 and i can run my pixel perfect report successfully. I now want to copy the same report and use it as a template to built report No.2.
I have tried to use the Export / Replace function in Nprinting but receive a message saying 'No matching connections' and the process fails. We are utilizing the same connections and server as the successful report. I have also tried using the Import function on the template editor itself and it also fails.
Is there a step i'm missing?
Thanks
Stewart
Hi Lech, Stuart
Sharing our findings after resolving this issue. Turned out there were four chart objects listed in the logfile C:\ProgramData\NPrinting\Logs\nprinting_webengine.log associated with a warning message when the report import was attempted:
Report does not match↓Missing objects from template: O\dCtWy, O\XzxpBF, O\pqJjQm, O\pyQB
When these were identified, we found no connection was associated in the template designer tool, so they had to be removed and re-added. Once this was done and the template saved, the report ran OK.
Hope that helps.
Regards
Chris
In the Designer, you are able to see a button ‘Save as’ à click on that it saves a .npx file (Nothing But report Template)
After that when you create a new report, use that .npx file as our template. Hope this solve your Issue.
Well well well..
First of all you did NOT build a pixel perfect report using Qlik Sense and NPrinitng 16 simply because NPrinitng 16 does not support Qlik Sense!!!
I think you need to get this sorted first, or maybe just clarify before you can go ahead with the next steps.
Now down to a way you can do this - you can follow my steps or watch the Youtube instruction - link below:
Thats it. It worked for me without any issues.
More info here:
https://help.qlik.com/en-US/nprinting/September2017/Content/ReportsDevelopment/Import-reports.htm
Import, export and replace reports - Qlik NPrinting - YouTube
cheers
Lech
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.
Hi Lech, Stewart
We have a similar issue importing a v17 report that was previously exported from the same.
The report is a PPT template connecting to a Qlik Sense app. The connection is verified OK, metadata loads fine, as does exporting the report template. When importing the exported ZIP file though, the wizard fails to identify the connection.
Works fine for other reports, but not this one for some reason.
I have this open with Qlik support so will post here once I get a resolution.
Regards
Chris
hi Chris. Please keep us posted what are your findings. It will be good to know what is the root cause of this problem in your case. Thanks
LEch
I would also love to hear if you make any progress with this eightieschild. I have the exact same problem you describe. I think it's possibly only started to happen since we upgraded to the latest version of NPrinting...
Hi Lech, Stuart
Sharing our findings after resolving this issue. Turned out there were four chart objects listed in the logfile C:\ProgramData\NPrinting\Logs\nprinting_webengine.log associated with a warning message when the report import was attempted:
Report does not match↓Missing objects from template: O\dCtWy, O\XzxpBF, O\pqJjQm, O\pyQB
When these were identified, we found no connection was associated in the template designer tool, so they had to be removed and re-added. Once this was done and the template saved, the report ran OK.
Hope that helps.
Regards
Chris
Thanks Chris now I can solve my problem!
Thanks Chris - that logfile has also been the key to fixing it for me too.
I had basically the same error as you in the logfile. In my case, the underlying problem was slightly different (object had been removed from the source QVW) but the reference to an object in the logfile was the vital clue.