Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi, This is more of an discussion of WHEN will it happen?
I know that we can use the API to trigger Nprinting tasks however when will triggering be easier to use?
The LDAP integration in Nprinting took a while to get introduced however now the "only" major feature that is missing is to be able to trigger a Nprinting report directly from the QMC.
This is what i want in QMC (whenever you create a distribution task in qlikview😞
"On Nprinting....."
Anyone know when this will be able in QlikView QMC?
The other thing is that we're looking at a new API end point to trigger User Import tasks as well. Currently, publish tasks, reload tasks, ondemand requests can all be started via API, but not User Import tasks. Also i'd expect a desire to chain a user import task + a publish task together, which could be doable with an API call too . Probably doing this with the UI (more work) could come later. Any thoughts on priorities for making NPrinting more operationally functional for bigger user bases or more dynamic user bases ?
one more - i know its not quite what you asked for but there is a sample QVW in this posting that you can schedule with publisher in order to call an NP task. Just test/set it up first with QV desktop to make sure it works ok.
Hi @JonnyPoole
That is a great news. I guess the other missing bit is connection metadata generation reload via API . This is just from top of my head, because i would already have few usecases where this feature would be handy.
you are absolutly right - i missed "reload" string in post /connections/{id}/reload oh well - that all means i can now achieve a lot more than before 🙂
regarding "import API trigger" i understand that there is no commitment yet but, is there anywhere in new community a wishlist for features (QlikView, Qlik Sense, NPrinting etc...) where we could like/vote and therefore provide priority indication? I think it would be a great way of engaging users in product developement. Apologies for going of the topic!
thanks
Lech