The task will distribute the report to the specified users via email, but you want to filter the recipient, not the task.
This can be done with the Recipient Import task: How to Create and Import Recipients with Filters and Distribution Groups
Then when the recipients are added to the Publish task, each one will have filters for his/her own data applied. A single task will distribute the reports to all of your intended recipients.
If you are using NPrinting 17, here is the tutorial around user import: Importing users with filters and groups ‒ QlikView NPrinting
Thank you. Please bear with me...
So, I need to need the Recipients I've already imported and import them again? But this time, add a Filter to each one? If so, is this the filter used to select them in the QV data? Is there a way to set up one filter that acts kind of like a variable that uses the email address to make the employee selection in QV?
Then, when I run the task, it will look at each Recipient (and the associated filter) and execute as desired?
I'm using nPrinting 16.
Correct, each recipient will need a filter(s) associated with them to make the proper selections in QlikView at the time their report is generated.
The email address you have associated with the recipients right now is for report distribution purposes only; it will not "select" that recipient in the QVW.
If you want to make the selection based on the email field in QV, that's fine. In that case, the filter would be the name of the email field in the QVW and the respective value for each recipient.
Then for the report task, it will go thru each recipient and select their email address in QV before generating the report.
Stephen, thank you for the replies. Last week, I set up everything the way you outlined it (I think). Got it ready for the first run this morning and ran the job. Everyone got an email, but the data in the email was for one person - the same person. It's like the employee filter did not apply. I have filters set up and assigned to the recipient, report, and task. Feels like I'm overlooking something simple. Why would the employee filter not work?