topic Re: Filters applied on empty report generated errors in Qlik NPrinting

Filters applied on empty report generated errors

griffinleow — Sat, 16 Nov 2024 03:11:02 GMT

I encountered the following behavior in NPrinting designer 17 and I want to check if this is an intended behavior.

My current set up is Qlik Sense connected to NPrinting, where data is loaded into QS dashboards. There will 2 QMC tasks that will reload the metadata and trigger NP publish tasks via API. Filters for the .xlsx reports are applied in NPrinting.

Just last week, there was a day when no data from the source was sent to QS. As such, it is expected to see empty rows in the .xlsx report. However, there was no .xlsx report generated for this particular day. I troubleshooted the issue in NPrinting designer to see if there is anything wrong with the applied filters and the report template. However, when I clicked on 'Preview' in Designer, an error message was generated stating that the error is due to the NP filter.

I suspect that NP filter cannot be applied on an empty report. Is there any way for the .xlsx report to be generated even though there is no row or data?

Thanks

Re: Filters applied on empty report generated errors

Ruggero_Piccoli — Wed, 26 Jun 2019 10:32:21 GMT

Hi,

I think you are experiencing:

If the application of a filter results in an impossible selection, a specific error is returned: "Cannot apply filter {0} to current document data. Requested fields with evaluates are: {1}",

from http://help.qlik.com/en-US/nprinting/June2019/Content/NPrinting/ReportsDevelopment/Static-dynamic-filters.htm

Best Regards,

Ruggero

Re: Filters applied on empty report generated errors

Frank_S — Wed, 26 Jun 2019 15:44:01 GMT

In addition to Ruggero's comments

You may wish to utilized the following task settings to manage email distribution when report errors are encountered.

https://help.qlik.com/en-US/nprinting/June2019/Content/NPrinting/AdministeringQVNprinting/MonitorKillTasks/Task-executions.htm#anchor-6

This feature is included with April 2019 NPrinting releases and later versions only. June 2019 is now available and I suggest upgrading to that version to leverage the most recent updates, bug fixes and performance enhancements.

hope this helps...

Re: Filters applied on empty report generated errors

griffinleow — Thu, 27 Jun 2019 01:40:22 GMT

Hi Frank,

Thanks for your reply, it was very helpful to learn of the new feature from April 2019 onwards.

We will try this out if this works for our case.

Regards,

Griffin

Re: Filters applied on empty report generated errors

griffinleow — Thu, 27 Jun 2019 01:48:43 GMT

Hi Ruggero,

Thanks for your reply.

Now that you mention this, it does seem like the root cause in my case. I would like to clarify further on this.

If the application of a filter results in an impossible selection, a specific error is returned: "Cannot apply filter {0} to current document data. Requested fields with evaluates are: {1}",

This particular report contains a filter on 2 fields applied. Based on the above, it means that if there is no data when filter for the 1st field is applied, it will result in an impossible selection when the filter for the 2nd field is then applied. Is this understanding correct?

In addition, there is another report that is empty but is being generated on a particular day. Similar, this report contains a filter on 2 fields. We checked in QS dashboard and applied the filter on the 1st field (via filter pane), and there was data/rows. The filter for the 2nd field was then applied, and there is no data/rows. Based on this, I am inferring that a filter cannot be applied on an empty dashboard. Is this understanding correct too?

Thank you

Re: Filters applied on empty report generated errors

Ruggero_Piccoli — Thu, 27 Jun 2019 08:35:21 GMT

Hi,

Yes, you understood correctly.

Best Regards,

Ruggero

Re: Filters applied on empty report generated errors

griffinleow — Fri, 05 Jul 2019 03:53:07 GMT

Hi Ruggero,

I clarified about the following behavior previously:

However, we begin to see a different behavior for the second case. In the dashboard, the first filter ('Evaluate Value is' in NP) applied returns some data. When the second filter ('Value is' in NP) is applied, it returns zero records. However, the report is not generated and throws an error out mentioning something about the filter.

Could you kindly advise what could be the issue here?

Thanks