Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello All -
We are finally migrating from NPrinting 16 and I'm getting an error on a task:
Failed generation of report 888acc18-254b-4bf0-b841-dac4bc809cda for user 91d5fe9e-d6e7-427f-a0e3-314d76841ac6. ERROR: Filters applied to user and report 888acc18-254b-4bf0-b841-dac4bc809cda define an empty set. |
How do I figure out the report and user from those ID #s?
Thanks!
If your main objective is to solve the 'empty set' issue, then finding the specific user is not necessarily essential.
What's happening is that the same dimension is being used as a 'report' filter and a 'user' filter.
Rules
Qlik NPrinting filter rules provide predictable behavior with a limited number of options:
Evaluated values are calculated first, in order to have static values to manage.
Filters will not necessarily overwrite past selections. There is no strict hierarchy.
Each filter will be analyzed in sequence: task -> user -> report -> object.
The values of filter fields at different levels will be intersected.
If the intersection gives an empty result, the filter chain will become invalid.
Try removing the filter from the report associated with the publish task that is generating this issue then run the publish task again and let us know if the issue is resolved.
Kind regards...
If your main objective is to solve the 'empty set' issue, then finding the specific user is not necessarily essential.
What's happening is that the same dimension is being used as a 'report' filter and a 'user' filter.
Rules
Qlik NPrinting filter rules provide predictable behavior with a limited number of options:
Evaluated values are calculated first, in order to have static values to manage.
Filters will not necessarily overwrite past selections. There is no strict hierarchy.
Each filter will be analyzed in sequence: task -> user -> report -> object.
The values of filter fields at different levels will be intersected.
If the intersection gives an empty result, the filter chain will become invalid.
Try removing the filter from the report associated with the publish task that is generating this issue then run the publish task again and let us know if the issue is resolved.
Kind regards...
Thank you! I'll give that a try.