Yesterday we've upgraded from 3.1 SR1 to 3.1 SR2, this is working good, all apps were migrated, etc.
But NPrinting (17.2.2) is working really weird with our reports with levels. They show me random orders and not properly setting the filter from the level.
I've tried to do another report with the same connection but still shows me random results
Level1= a, b, c
So my report shows me this
Obj1 = a
Obj2 = b
Obj3 = a
Obj1 = b
Obj2 = b
Obj3 = a
Every time with random results from the filter.
What can I do? Re-do connections? Filters?
I hope that you can help me, we need to fix this asap
I went with option 2 and had no issues. I now have Sense and NPrinting on June17 and everything is stable.
Reminder: When you upgrade NPrinting, backup the following directories, so you don't lose your certs:
Then when the install is complete, copy your backup .key, .pem and app.conf back to the appropriate directory.
Some news here.
We finally have Qlik Sense and NPrinting June 2017 working together.
This steps we did to upgrade:
1.- Upgrade QSense from 3.1 SR1 to 3.1 SR2 (Synchronized Persistence)
At this point, we check if NPrinting was working with this new version of Sense, but was working really weird, filters orders, object, etc.
So we tried to keep upgrading Qlik Sense:
2.- Upgrade QSense 3.1 SR2 to June 2017 (Synchronized to Shared Persistence).
Now our reports was generating fine, but some object don't show properly (KPI object shows me a number without format, or some text objects didn't appear on my report)
So we decide to upgrade NPrinting.
3.- Upgrade NPrinting from 17.2.2 to 17.3
Reports was generating in the same way of step 2 and was similar (same KPI without format and text objects dont show texts)
4.- Upgrade NPrinting from 17.3 to June 2017
Our reports was generating in the same way as above, but our Qlik Sense app was showing this KPI without format in the same way (I think is a problem of the object on the app and not from the generated report)
So now we have NPrinting and Qlik Sense working together on June 2017.
Thank you so much for your help, and I hope this can help someone in this same scenario too
PS: My english isn't good, but I hope that you can understand.