Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi all,
we have a customer which wants to use NPrinting as a Self Service Tool for their own business User. I would like to know which are the Best Practises for a scenario like described below:
Now I have the following questions:
Thanks for your input!
Regards,
Patric
Best practise for nprinting would be create a dedicated app for nprinting full stop. keeps the visualisations available under your control and the size of the app down which will improve processing speed. link the refresh of this app to the main app via qvds to optimise the task reload speed. new visualisations are then available under control of the owner of that app.
If you want them to create new reports then you need to make them developers in nprinting to access the report creation feature. limiting their data access can be done as you suggest by section access on the nprinting app in sense.
Some of the questions you raised nsq files are only in 16 v17 that connects to sense doesn't have this concept.
Hope this gets you started.
Regards
Andy
Hi Andy,
thank you for your answer.
We are using NPrinting 16 and Qlikview 12.
So correct me if i am wrong creating a reduced app for every NPrinting User (Business User who will be a Developer in Nprinting) would be the correct solution.
The problem here in my understanding is exactly the step of the data redcution as NPrinting 16 does not support Windows NT authentication so this means it can not handle the reduction of data through Section Access via NTNAME.
In this case my Idea would be to create a main NPrinting project which is repsonible for the "Loop and Reduce" functionality, for distributing the reduced Qlikview App to those users in a specific user folder (similar to the Publisher capability). In this case we would have to create a copy of the main app (only for NPrinting purpose) without Section Access feature to take it as input for the distribution of the reduced app to the NPrinting users. So at the end the users could work on the own reduced .qvw app file for the creation of their own NPrinting Reports.
Further all NPrinting users can be defined in a specific AD group and those recipients could be retrieven and loaded directly from a Qlikview App (ex. table object).
Does it makes sense?
Regards,
Patric
Hi,
few questions you need to consider:
I reckon you should consider following scenario:
What i do not understand is why you would like to work on separate apps when building NPrinting reports? I see benefit of it only in data volume and it may be vary beneficial in that aspect.
Other problems with NPrinting 16 is that you cannot have multiple projects running at the same time on server. NPrinting 16 is not multi threaded so it will be extremely slow and multiple developers can design their apps at the same time, but automated execution will be queued anyway when projects will be placed!
I guess you do not have publisher, right?
regards
Lech
Hi Lech,
first of all thanks for ur answer.
To ur points:
- Every user should see only the own data this is why the multiple apps and the loop and reduce proposed solution. Section Access via NT Windows Authentication is not working with NPrinting so we have to go for other solution.
- Nprinting 17 was not recommended by Qlik to us as the product is still not mature
- About self service by business user creating templates etc. was not recommended by us but the client insisted so he is aware about the risk.
Regards,
Patric
my comments on your points:
- Every user should see only the own data this is why the multiple apps and the loop and reduce proposed solution. Section Access via NT Windows Authentication is not working with NPrinting so we have to go for other solution.
- Nprinting 17 was not recommended by Qlik to us as the product is still not mature
- About self service by business user creating templates etc. was not recommended by us but the client insisted so he is aware about the risk.
That is my point of view.
I usually ask what is a customer requirement, how they want to use tool etc... but my question is usually how they will use it - not how they will develop in it.
Developing reports in NPrinting is probably more difficult than developing in QlikView and you need to be experienced in both. If those customer developers will have this knowledge they would not ask you for recommendations i guess.
Please reconsider NPrinting 17 as it may solve most of your bullet-points!
cheers
Lech
Thanks again.
As for the training we already had several sessions with them. I completely agree with ur points about it which I also mentioned as possible risk. I think we will take in consideration ur inputs. Thanks!