Qlik Community

Qlik NPrinting Discussions

Discussion Board for collaboration on Qlik NPrinting.

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Not applicable

Best practice for recipient import

Hi Community,


There are several ways to import Recipients, like Excel, Outlook, AD and DB.

What I am concerned about is when personnel change happens in a company, taking Excel import as an example, they need to update the import file manually every time so that the Recipient list in NPrinting are updated.

Is there best practice that the imported file can be updated automatically while personnel change is happened? Is using import file by AD list a good way in this case?

But I am considering whether AD list can handle filter field rather than editing each recipient's filter in NPrinting after importing the AD list.

Thanks.

Tags (1)
1 Solution

Accepted Solutions
Highlighted
Support
Support

Re: Best practice for recipient import

Hi Eddie,

I guess you will need to work out what suites you best. If you are using a QlikView document as the source for your Import Recipient entity, clearly you will only have the latest list after a reload. If your HR DB is updated frequently and you need the latest list say every hour, you would probably get the list directly from the DB. Of course this is assuming your QlikView document is reloaded less frequently than your NPrinting recipient import task is run.

Best,

Daniel.

View solution in original post

7 Replies
Highlighted
Partner
Partner

Re: Best practice for recipient import

hi

from my experience

the best way to handle recipient

is to use the same table you use to manage the qlikview users 

and load this table every morning to the qv model

so nprinting is loading the recipients list from the qlikview model

Highlighted
Not applicable

Re: Best practice for recipient import

Hi Liron,

Thank you very much for your suggestion.

May you illustrate‌ how to import the table from qv model to NPrinting Recipient list?

Highlighted
Support
Support

Re: Best practice for recipient import

Highlighted
Not applicable

Re: Best practice for recipient import

Hi Daniel,

Thank you for your help.

Based on your idea, I think out a new idea.

The NPrinting recipient import connect to HR DB which has the latest employee list.Then scheduling the import task.


Is it more efficient from the above practice? It is because I also need to connect to HR DB in QV document from the practice of loading recipient table from QVW. NPrinting can allow users to import the updated recipient information from DB directly.

Highlighted
Support
Support

Re: Best practice for recipient import

Hi Eddie,

I guess you will need to work out what suites you best. If you are using a QlikView document as the source for your Import Recipient entity, clearly you will only have the latest list after a reload. If your HR DB is updated frequently and you need the latest list say every hour, you would probably get the list directly from the DB. Of course this is assuming your QlikView document is reloaded less frequently than your NPrinting recipient import task is run.

Best,

Daniel.

View solution in original post

Highlighted
Not applicable

Re: Best practice for recipient import

Dear Daniel,

Thank you very much for your clear explanation.

Highlighted
Master
Master

Re: Best practice for recipient import