User import NPrinting 17 November 2017

[lauranvh]

For this case we are in a transition from QlikView to Qlik Sense and from NPrinting 16 to NPrinting 17.

A client wants to send his employees and customers reports via NPrinting 17 but we’re experiencing difficulties with the user import of all these different recipients.

There are about 1000 recipients in their system. The client doesn’t want to maintain an Excel file with all the users / filters and groups and will not create all the users by hand. Instead we tried to create a different solution that doesn’t need a lot of work by hand.

Our question is how can we create a suitable, scalable and workable solution for this problem. That can be sustained for a large number of recipients that can add filters, groups to NPrinting 17 easily and doesn’t require a large amount of work.

I’ll try to sketch a case for this problem:

In NPrinting 16 we created multiple NSQ’s to send information to recipients. We imported the recipients / filters and groups for that NSQ from a QlikView Object in the same QVW as the data was in. These recipients could be Employees but also Customers. Also the Employees can be Customers in this case. In NPrinting 16 it’s possible to have multiple user groups in the different NSQ’s. This is not possible in NPrinting 17 because the e-mail address is the limiting factor. So now we wanted to create an import file for NPrinting 17 that imports all of these users / groups and filters.

We tried to create a Qlik Sense App that imports a employees table (qvd) into the datamodel. Than do some transformations and use that data to create three tables (Users / Filters / Groups). In these tables there are a lot of IF statements to check if for example someone is in a group or a department so he/she has to receive a report, has to be put in a certain group or gets a filter. Than we created a NPrinting connection to the app, created a Excel report with the 3 tables in the correct format and created a task that puts the Excel report in a folder. Now we create a import task that imports the users/filters/groups into NPrinting.
As we found out this method isn’t manageable and can’t be sustained when we add filters, groups or recipients from a different source or for different reports and filters.

Our question in this case is, do you have a solution that can be sustained for a large number of recipients that can add filters, groups to NPrinting 17 easily and doesn’t require a large amount of work.

[Ruggero_Piccoli · Accepted solution]

Hi,

In Qlik NPrinting 17+ at the moment (April 2018), you can create users in 3 ways:

1. manual
2. by importing from an Excel file. It must have the same structure of the example you find in the page https://help.qlik.com/en-US/nprinting/April2018/Content/DeployingQVNprinting/Import-Users-Filters.ht... because you cannot map a file with a custom structure as you can do in Qlik NPrinting 16
3. by using APIs https://help.qlik.com/en-US/nprinting/April2018/Content/Extending/Intro-Extending.htm. Details about APIs that you can use to manage users are https://help.qlik.com/en-US/nprinting/April2018/APIs/NP+API/index.html#Users. For example they were used to develop this thiurd party app https://github.com/qlik-oss/nprinting-adsync to import users from an active directory domain.

So if 1 and 2 are no working in your case the only other way is to develop a custom application that uses the APIs.

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.

[blaise]

I have a client that has some of the same issues / concerns as you.

We have created a single qvw that collects and combines all excel export from NP Published tasks (these tasks extracts the info from qvw's). This way we have 1 import tasks that takes care of all import of users and filters / groups.

This works OK but we have some issues with this task and the checkbox "remove users..." if someone has changed a user in Web Console, so we have unchecked this checkbox and are planning on running some API to remove users not needed anymore.

The API solution as suggested by rpc‌ might be a better one though as API instead of import task means better control.