topic Re: NPrinting June 2020 Filter fail in Qlik NPrinting

NPrinting June 2020 Filter fail

Anders_Eriksson — Wed, 08 Jul 2020 08:39:29 GMT

Monday July 6th I updated Sense and NPrinting from February 2019 to June 2020.
Before that all scheduled reports in NPrinting worked, after every report using a filter fails.
Only the one report not using a filter works?

In order to narrow down the problem I have made a new extremely simple Sense application.

Load script in Sense application is;
Data: load * inline [
   Year,   Value
2020,   100
2019,   80
2018,   60
2017,   40
2016,   20
];

GUI is one straight table with Year as dimension and Sum(Value) as measure.
In NPrinting I created a new app, new connection to the new Sense application, new simple filter (Year=2020) and a new HTML report.
NPrinting HTML report connected to this application displaying the table without filter works in preview in NPrinting Designer.
Adding the filter (Year = 2020) to the table in NPrinting Designer it fails in preview.
Error stated: Invalid selections are applied to chart O\LQvzd: Filters: [Fields: [Name: F\Year, ConnectionId: 827f9899-2495-4bc1-8bfc-7649efd5b5b5, Values: [String:2020], Override:False, Void: False, SelectExcluded: False], Variables: [], Void: False], Bookmark: , Void: False
Using a publish task same thing happens, works without filters, filter in either report or task it fails.

New Sense application, new nPrinting report and new NPrinting filter, all extremely simple, still it fails when filter is used.
Nothing in the logs, neither NPrinting logs nor Windows Event logs.

What is going on?
Anyone had a similar problem?

Re: NPrinting June 2020 Filter fail

Anders_Eriksson — Wed, 08 Jul 2020 08:37:46 GMT

ps have opened a support case for this yesterday but as yet no action in that.
All but one daily report are failing due to this.

Re: NPrinting June 2020 Filter fail

Lech_Miszkiewicz — Wed, 08 Jul 2020 10:26:20 GMT

What is your simple filter? Is it:

1 --> value is = 2020

2 -->numerical value is = 2020

It is very significant difference and it depends on datatype of the filtered field! - https://nprintingadventures.com/2019/02/15/the-pitfalls-of-nprinting-filters-part-1-dates-and-duals/

Also - after upgrade did you reload all connections metadata as per requirements?

Re: NPrinting June 2020 Filter fail

Anders_Eriksson — Wed, 08 Jul 2020 13:02:59 GMT

My simple filter was alternative one: value is = 2020
Purely by coincident I made it a numerical field.
You were spot on, changing it to numerical value is = 2020 the filter worked!

The old reports that worked before the update did not have exactly this.
Instead those filters have a field that is dual and the test is: value is = Online
Works when changing it to instead test for the numerical value of the dual: numerical value is = 1
Strange that it worked before the update of Sense and NPrinting.
Looks to be some sort of breaking change in the handling of data types?

Reload metadata I did yes.
Update to June 2020 I needed to fetch new certificate for the connections to Sense.
after installation all of the connections were updated.
Also the simple test was on a completely new Nprinting app/connection created
after update eliminating any dependence on configuration in previous version.

Thank you Lech for the most appreciated help!

Re: NPrinting June 2020 Filter fail

Lech_Miszkiewicz — Wed, 08 Jul 2020 22:50:55 GMT

Hi @Anders_Eriksson

Filters were always having this golden rule in NPrinting 17+, for text you had to use "value is", for dual ,integers, dates etc you had to use "numerical value is" for the filter to work properly.

I am not saying your filter previously did not work, all what I am saying is that it was not setup properly.

Glad I could help.

thanks

Lech