Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
i see several blogs to call nprinting tasks using qliksnese load script via rest apis.
can we call OnDemand nprinting requests via qliksense load scripts too.. for applying some dynamic filters in nprinting..??
When you say: "sometims while providing the btton to users, we seee , users complains they camt generate reports, as they might need to login npringing before pressing ondemand button..." That indicates to me potential issues:
For properly working OnDemand Button with Qlik Sense and NPrinting you must ensure all requirements and setings are met: https://help.qlik.com/en-US/nprinting/February2025/Content/NPrinting/On-Demand/Create-Report-On-Dema...
There are also youtube Qlik support videos explaining this issue well:https://www.youtube.com/watch?v=eHVBVoLy16Y
Troubleshooting those issues does not take much time and if company policies are well maintained there should be no issue with this feature.
cheers
Hi,
You can use the Qlik REST Connector, and use this endpoint: Qlik NPrinting API − post /ondemand/requests | Qlik NPrinting Help
Best
Personally I dont think those end points will work given that they work very differently. The API endpoints we normally use within load script are for actions which are triggered and dont require interactive interface.
I dont think content types from https://help.qlik.com/en-US/nprinting/February2024/APIs/NP+API/index.html?page=45 will be supported in load script.
cheers
do you have any sample code to refer calling those ondemand apis in Qlik sense load scripts??
Hi @vimalthehero - that is question to @mpc as he said you could use it in load script.
I personally see no reason using this OnDemand Api in load script. Everything you need can be achieved using other APIs (Filter & task Api) which we know works in Load script and to apply dynamic filters (whatever you mean by that).
It just look like you are overcomplicating things which can be simpler just by using different solution you have not thought of yet maybe?
Maybe you could share scenario so we could try replicate and suggest you maybe different solution which would give you the same end result.
cheers
Users will request reports via a Teams chatbox. These requests will trigger an automated process in Qlik Sense to generate the reports based on their specified filters. The generated reports will then be stored in SharePoint for users to access at any time, and they will receive an email notification upon completion.
Note: user wont have access to Qlik Nprinting ondemand report genration directly..!
all users requests will be procces via qliksense load script..
Have you considered that for some things you mentioned there are no existing solutions and you will have to build your own piece of soft to support it?
I see lots of issues with your initial proposal:
Your process looks cool but I cannot see it as a reliable solution as all steps have equivalent in real world but they were designed to work differently.
I may play with API to see if I could trigger simple OnDemand task - but I will do that in my free time as I would have to decipher how requests have to be built and understand how whole process works from API side.
I dont have much more constructive comment at the moment - sorry.
I appreciate your feedback. The following are some of the approaches I plan to implement in response.
Currently im trying to figure out the nprinting api call in Qliksense load script, which will be a parent report to run all the nprinting user requests..and figuring out the task exectuign api call
This is why I have issue with this approach. Many assumptions you were taking are not simple or possible.
Given the responses I am getting in this chat I am not sure you are aware how much consideration you need to take to each of the questions I previously asked as your answers were not taking into account limitations of the existing API and some of the things you are saying you are going to do are just impossible.
I am also providing comments under your comments in next response to your comment.
cheers
cheers