Filters in Nprinting Report

[yashcena]

I have created two nprinting reports which have to be filtered for two columns L3 and L4 respectively when sent to users (Report1- L3 filter, Report2-L4 filter)

I have to make use of an excel sheet which will have the list of all users and the filters that have to be applied on the reports which they receive.

I created an excel sheet and an import task to fetch the users and filters. Here's the issue with it:

If a person A is supposed to receive Report1 with L3(1) filter and Report2 with L4(1) filter, then the import task applies both L3 and L4 filters on the user account. Thus, A will receive Report1 with L3(1) and L4(1) filters applied together.

Similarly, If a person B is supposed to receive Report1 with L3(2) filter applied and Report2 with L4(2) filter applied, he/she will receive these reports with the two filters applied together.

The import task which uses the excel sheet is messing up the filters.  Since the import task will apply the filters at user account level, it would create problems for other reports that they are receiving because Nprinting will now apply L3 and L4 filters on every report that they are scheduled to receive. Since only Report1 and Report2 have L3 and L4 columns, users will receive blank reports for other reports other than these 2 because L3 and L4 filters will not be applicable on any other report.

To avoid this issue of filters, I created individual task for each recipient and added filters (L3(1), L3(2), L4(1), L4(2)......) at task level. The same person is supposed to receive multiple Report1 with a different L3 filter applied each time so I have created multiple tasks for each instance.

But maintaining this list of tasks would be tedious when the number of receipts increase. Is there a better way to this?

I hope I have made my requirement and the issue that I'm facing clear.

Thanks,

YASH

[lauranvh]

It is possible to make multiple connections to a single QVW/QVF.

So the L3 filters can be appointed to connection L3 and the L4 filters can be appointed to connection L4 to create the differences.

You can leave the user import file is as because the user can have multiple filters that are appointed to different connections. So which report is scheduled will determine which filters are being used.

[yashcena]

Thanks Lauran!

I have one more question- The same person is supposed to receive Report1 with different L3 filters applied. So even if I separate the connection for Report1 and Report2, the two L3 filters would still apply together on that user.

Is there a work around for that? If I create multiple connections for each filter, it would be same as creating different task.

Thanks,

YASH

[lauranvh]

There is a difference between creating a task and a connection.

The task uses the connection. And it's possible to apply a filter on a single connection. So you can have multiple filters on a user that will not be used when they are in a different connection.

But for the problem with different L3 filters you need to make another connection I think. They will applied both when they are in the same connection and the same user.

Would you like to add a example user import file that you are using?

[vvvvvvizard]

Create filters only when the filter needs to  be applied to all users , use set analysis instead and create multiple objects for the different users locked with their selection

[Anonymous]

Not sure what version of Nprinting you're using.

You could try multiple excel files (or spreadsheet tabs) to import the users and filters between report runs.  So excel file 1 would have users and filers for the first report.  And excel file 2 would have users and filters for the 2nd report.

So your job would be

Task 1 Import recipients and filters for report 1

Task 2 Report1

Task 3 Import recipients and filters for report 2 (override previous recipients and filters)

Tast 4 Report2

[Anonymous]

We sitting with a similar issue at the moment too, will try and replicate the above breakdown and see. We hover are looking at going 3 levels down so this just becomes one nightmare to manage.