The recipient import file has two identically named filters
One filter is associated with one NP connection
The second filter is associated with a separate NP connection
BOTH NPrinting connections are embedded within the same NPrinting APP
Error when running the Recipient import: "Result: 202xxxxxxxxxxxWarnImporting FILTER with name 'Year-XXXX' : skipped because another filter with the same name and app exists in the import data"
Environment
All supported versions of NPrinting
Resolution
In your recipient import file, ensure each filter name is named uniquely so that you understand which NP connection that the filter belongs to. This will ensure the import does not error on a duplicate filter names
Cause
This is working as design
Since Identical Filter names cannot be parsed in the recipient import file with respect to applying filters to users within the file, the import process rejects the duplicate filter name
NOTE: it is understood that it is possible to enter duplicate filter names in the NP web console and there is no warning preventing this action. However, it is strongly recommended to follow the best practice of uniquely naming ALL filters in either the NP web console and in the recipient import file. This will also mitigate other unexpected NPrinting report and publish task errors due to identically named filters.
