App1 Internal ID 1 - main dashboard used to create the NPrinting report with (On Demand selections dashboard)
App2 Internal ID 2 - secondary dashboard added to the On Demand button 'NP Connection/App' field. (secondary NPrinting Connection/App NOTassociated with the NPrinting report)
both apps contain identical objects and object IDs
A Qlik Sense On-Demand custom object button inserted in our main dashboard.
Our main dashboard is used to create an NP report
The On Demand button is in turn connected to the secondary dashboard (a copy of the 'main' dashboard) in the 'NP connection/App' field
After upgrading Qlik Sense recently we are noticing errors in the Qlik Sense NPrinting On Demand Object or when attempting to generate NPrinting reports in the Qlik Sense hub
Result:
Warning or error message in On Demand button 'connection' field appears
Environments Affected
Qlik Sense Server February 2020 and later versions
Resolution
Ensure that the Qlik Sense dashboard used to create the NPrinting report is the same dashboard used in the Qlik Sense On Demand report button - "NP connection/App" field.
Cause:
It is necessary to use the same NPrinting connection/app for the dashboard from which the NPrinting report was developed with (in this example, the Primary Dashboard is the source data for the NPrinting report) rather then the NPrinting connection to the secondary identical dashboard.
Why?
Qlik Sense On Demand selections need to be made in the same QS dashboard which is the source data for the NPrinting report. Doing otherwise will, as expected, result in errors and warnings.
NP connection/App changes in Feb. 2020 Qlik Sense NP On Demand objects were introduced to enable seamless On Demand report migration between Qlik Sense environments (ie: DEV to PROD)