
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nprinting 16 Cycle and filter
Hi Everyone,
When we have a cycle in Nprinting and récipients with filters, nprinting produce report for the cycle and the récipients.
eg.
cycle = région_code
james filter : region_code = 1
john filter: region_code = 2
ana filter : region_code = 3
First Nprinting générate all region_code from cycle
Then Nprinting produces separate reports for each recipients.
Basically, he produce reports twice, which is a huge waste of time and resources.
It would seem logical to send the reports generated by the cycle to specific recipients.
Possible ?
Thanks.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Sebastien,
I would say don't use Cycle if your user filters do the job. If you are using the Cycled Field value in Dynamic naming you may need to think of some other creative way to get the same result - perhaps with a QlikView variable with value something like =GetFieldSelections([region_code])?
HTH - Daniel.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Daniel, but if i don't use Cycle, there will be another problem.
A manager with 2 regions will receive an aggregated report from both regions and not two reports


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
You can evaluate to use Pages or Levels in the report template. The created report will have the data from 2 regions but not aggregated. They will be divided into two pages or two levels in the same page.
Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.
Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Ruggero, it's a good idéa but not possible with my report structure.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's insane that a tool makes several times the same thing, it's a huge waste of time


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Qlik NPrinting produces different reports for different users because they have different filters.
Qlik NPrinting 17+ has a lot of internal optimizations to speed up the production process. The version 16 that you are using also has optimizations not visible by the user.
Qlik NPrinting 17+ is also multi-thread so it can take advantage of multicore CPUs.
Another important thing is that cycles, pages, levels and filter are in fact all filters. To create a page or a report as result of a cycle Qlik NPrinting must calculate ad apply the set of filters you added into the report configuration.
Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT https://community.qlik.com/docs/DOC-14806. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.
Best Regards,
Ruggero
---------------------------------------------
When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
