Description
When performing an NPrinting Recipient Import using the recipients import xlsx file, you notice that user filters are not available for use with NPrinting report table or image objects, NPrinting reports and NPrinting publish tasks.
To be more specific, when you open the Qlik NPrinting Designer to create or edit an NPrinting report, the template editor will load all filters (ie: filters that that can be associated with NPrinting table and image objects) with one exception.
Exception: filters that are already associated with a user and that are not yet used as object filters will not be available for use as table and image object filters.
- To understand the recipient import process visit the related content section of this article.
- To download a sample copy of the recipient import file, view the related content section of this article.
- To understand filter rules in general, see the related content section of this article.
Environment
- NPrinting: June 2020 and later versions
Solution
To enable imported user filters for general use:
(From https://help.qlik.com/en-US/nprinting/Content/NPrinting/ReportsDevelopment/Static-dynamic-filters.ht...)
- Navigate to "C:\Program Files\NPrintingServer\NPrinting\WebEngine"
- Make a backup copy of then open the webengine.config file
- Uncomment the line <!-<add key=’include-user-filters’/>
- Save the file
- Restart all NPrinting services
- This flag changes this default behavior mentioned above so that all filters associated with users will be loaded.
Keep in mind...
- If you make this change, it 'may' slow down your report development if you have many NPrinting users. The designer will need to parse all NP users in the NP database
- When upgrading NPrinting, you must ensure to perform this change as upgrading NPrinting does not port these changes. They will be overwritten during the upgrade process.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
Related Content
