Woah! Good to know, thanks! I'll just look for qv 11 sr13 or something then. Or leave it alone if I don't need totals on that particular object type. I hear nprinting 17 still has some issues being ironed out and friend advised me to stick to 16 for awhile if 16 is serving my current needs.
Actually, a colleague is using nprinting 16 designer and qv 12 desktop edition on another server environment, but they're using windows task scheduler and powershell to run the nprinting jobs instead of nprinting server. I'll take your word and leave qv12 alone for now. The powershell does some fancy stuff to rotate files into position for qlikviews to read, then tells nprinting to tell the qlikviews to reload themselves and grab TB01 off the front. After nprinting saves the file, the powershell moves the qlikview back out and pulls in another qlikview for the nprinting to run. So in that setup, nprintign designer's just like a little robot arm poking TB01 out of whatever qlikview powershell puts in front of it. (The powershell script is probably 20 pages long now, but it works for that purpose. ) My qlikviews and nprinting jobs are more complex, so I'm using nprinting server and qv server to run things.)
I'm sure you could get NPrinting 16.x to work with QlikView 12.x in some instances but it is definitely not supported. What this means is that if you do have an issue and approach Qlik Support, we will ask you to reproduce the issue in a supported environment before we can help.
Thanks Daniel. I think we'll take a page from NASA's book and leave well enough alone if we have a bug-free configuration with the older software right now. I do suspect the compatibility issue must be the server program if there's no apparent issue when a user uses nprinting designer to run a qlikview desktop. Or it could be issues with various object or report types. My colleagues are just doing a qlikview entity report for TB01 which is probably the barebones smallest kind of task nprinting can do with a qlikview. (They're just cleaning files before importing them to our database.) I think it's a windows 8 enterprise kind of environment they're in too. Operating system environment could be a factor.
I just want to add one thing - NPrinting always uses QlikView Desktop to access QVW files so even when using QlikView server connections (qvp://) it goes through QlikView Desktop - similar to File > Open in Server. That is why you need a properly licensed QlikView Desktop installed on the NPrinting Designer and Server machines (v16.x - if different) or NPrinting Engine machine (v17.x if the engine is used to access QlikView connections as opposed to Qlik Sense connections). Just thought you would be interested to know that.
Thx, as Nprinting 17 is still not having all the functionalities as version 16 at least till the summer i will stick to my current versions. I will need to migrate to version 17 if I want to use QV12 in the future but not sooner than that i hear that version 17 becomes equal on functionality as version 16 of nprinting.