Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I am using NPrinting On-Demand option. From Qlik Sense app, When I click the NP button I am seeing three buttons: "Close", "Quick Report", "New Report" as attached in the screen shot. Is there a possibility to just keep two buttons displayed "Quick Report" and "Close".
The problem of displaying "New Report" button is, it gives user's the option to select a incorrect template which eventually makes the report to fail. Basically trying to restrict the option. Pls advice.
No, there is no way to change that setting out of the box.
You may want to try and edit the extension to remove this functionality but you will do it at your own risk so make sure you keep the copy of it before changing the original.
and as an example you could just change "ng-click="go2SelectReportStage()" to "ng-click="exportReport()" tso regardless which button users click they will just generate report....
see screenshot:
Or you can hide the button all together....
Steps how to achieve this:
Having this in test environment would be probably the best...
No, there is no way to change that setting out of the box.
You may want to try and edit the extension to remove this functionality but you will do it at your own risk so make sure you keep the copy of it before changing the original.
and as an example you could just change "ng-click="go2SelectReportStage()" to "ng-click="exportReport()" tso regardless which button users click they will just generate report....
see screenshot:
Or you can hide the button all together....
Steps how to achieve this:
Having this in test environment would be probably the best...
Hi,
Thank you Lech for your recommendation and steps to customize the plug-in. It would be very helpful if Qlik provides an option to customize it appose to touching the developers taking the risk of manipulating it. Is there a possibility to have this feature in any of our future Qlik Releases?
I am not working for Qlik so i have no idea if such request can be part of future implementations.
on the other hand the change i mentioned should be “walk in the park” for any developer-there is no rocket science there-just simple type script...