Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
doherja
Creator
Creator

Undesired note about selections in NPrinting

Hello,

We are using NPrinting 16 SR9 and QlikView April 2019. (I am aware that this configuration is not supported, but I appreciate any insight that you my have outside of upgrading.)

Recently, charts as image, within an HTML report, have begun showing the note: 'Selection Status: No Selections.' I have confirmed the following:

  • 'Selection Stamps in Exports' property is unchecked in Desktop
  • 'SelectionStampInHTMLExport' setting does not exist in local settings.ini
  • 'SelectionStampInHTMLExport' does not exist in the server settings.ini (also, we are not using QVP)

The result is the same whether the report runs on the server or is run locally in NPrinting desktop. We have recently upgraded from QV April 2018, but the problem did not begin until some time later (there is at least one 'good' run of the report after the upgrade).

I will be grateful for any suggestions.

Labels (2)
1 Solution

Accepted Solutions
doherja
Creator
Creator
Author

Thank you, Frank.  It turned out to be caused by saving the qvw in Web view.  Turning off Web view and re-publishing fixed the report.

View solution in original post

2 Replies
Frank_S
Support
Support

So you are referring to the QV user settings/export tab just to be clear.

The export will occur under the user settings of the user that executes the report. 

Therefore if your 'user' settings in the QV desktop are different than other users including the NP service account, this is likely the cause of the issue.

To resolve, log on as the NPrinting service account and update the QV desktop user settings accordingly.

QV user preferences - export tab.PNG

Hope this helps.

 

Please remember hit the 'Like' button and for helpful answers and resolutions, click on the 'Accept As Solution' button. Cheers!
doherja
Creator
Creator
Author

Thank you, Frank.  It turned out to be caused by saving the qvw in Web view.  Turning off Web view and re-publishing fixed the report.