Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello Qlik Community,
We are excited to announce the release of the QlikView Governance Dashboard and QlikView NPrinting 17.
To learn more, see what our resident Jedi of BI PeggySue Werthessen has to say in her latest blog: Qlik Loves QlikView! | Qlik
and watch these brief videos.
QlikView Governance Dashboard in 60 Seconds
NPrinting 17 in 60 Seconds
We are currently testing compatibility with MS Office 2016. If/when the testing is successful, the requirements document (System requirements for QlikView NPrinting ‒ QlikView NPrinting) will be updated.
Office 365, however, is not compatible for template development. It can be used as a program to open reports, but template creation requires one of the compatible versions as per the requirements document.
Louis -
With regard to your question about .nsq migration, it is true that there is no longer an .nsq file for NP17. However, the repository that stores all metadata related to the reports, tasks, users, etc., can be moved from one environment to another with a command line tool that can be used to back up the DB and templates.
This will create a zip file for migration between environments. Clearly connections need to be “congruent” meaning that paths to QVWs must work in the “new” environment.
More around this process is available here: Backup and restore of a repository ‒ QlikView NPrinting
Office 365, however, is not compatible for template development. It can be used as a program to open reports, but template creation requires one of the compatible versions as per the requirements document.
This is really bad... We are upgrading now to Office 365 and NPrinting is not working anymore. Is there any workaround I can do to be able to work with it again?!
I agree with you, Nicole, although my concerns are directed at QlikView and Office 365. Since we "upgraded" to O365 I have not found a way to pull files and lists from SharePoint any more when one is in the cloud and the other is not.
--john
Good morning Stephen Jasionowski,
I see you are running tests for compatibility. Any estimates on when QlikView 12 and NPrinting 17 will be compatible with Microsoft Office 2016?
We have a possible conflict in our firm where the standard is changing to Office 2016 and we run NPrinting 17 and QlikView 12.
Any estimates are highly valuable.
Thank you!
Hugo -
I do not have an estimate at this time. It will not be part of the June release so please check back after that and I may have a better idea of timing at that point.
Good news! We completed our testing and Office 2016 is compatible with NPrinting 17.
Official documentation is forthcoming.
This is fantastic. Will communicate the customers about compatibility
Thank you
It's even better from memory utilization standpoint. I've installed NPrinting v17 IR. When you just start NPrinting services on a server it creates from 20 to 35 simultaneous connections to postgres database with repository. When you try to preview multi-page report it opens a new QlikView instance per each page if they fit in a memory and never close it after that. I've filed this as memory leak to support (00726358). The response was:
"NPrinting working as designed."
These memory leak cases were designed.
How To Download NPrinting Trail version. for Practice