Qlik Community

Qlik NPrinting Discussions

Discussion Board for collaboration on Qlik NPrinting.

Announcements
Attend QlikWorld 2020 and hear keynote speaker, Malcolm Gladwell. Register by February 29th to save $200. Learn More
Highlighted
JustinDallas
Valued Contributor II

NPrinting 17: Exclude Values - 'Failure Filter Materialization'

Hello Folks,

I have an NPrinting report with a filter that instead of selecting, I need to exclude certain values.  Right now, I've got my filter looking like this, which is wrong.

QNPrintingFilter.PNG

Obviously, this doesn't work and instead leads to the following error.

exception System.Exception: Failure Filter Materialization, fields with formula:

F\Bill To ID'. No report will be generated.

Does anyone know how to create an exclusion filter in NPrinting?

1 Solution

Accepted Solutions
Highlighted
Partner
Partner

Re: NPrinting 17: Exclude Values - 'Failure Filter Materialization'

Yo my knowledge, you cannot create exclusion filtering, all evaluation filters needs to be "evaluated" as a single value.

My recomendation would be to create the filter in the qvw/qvf instead à la "if(not match([Bill TO ID9,'value1','value2',valueN'),1,0) as _FlagNPValidBillTo or similar.

I don't like solutions where you have to alter the qvw for NP to work for most cases its better to either create a NP specific qvw or add NP specific fields to fulfil your reporting needs.

We will, in the hopefully not so distant future, have a reporting tool that can solve all needs without the need of alter the source documents.

In the best of worlds we could have filters on connections, evaluation criterias that returns multiple values and no limitations for source documents with triggers.

Br Johan

View solution in original post

1 Reply
Highlighted
Partner
Partner

Re: NPrinting 17: Exclude Values - 'Failure Filter Materialization'

Yo my knowledge, you cannot create exclusion filtering, all evaluation filters needs to be "evaluated" as a single value.

My recomendation would be to create the filter in the qvw/qvf instead à la "if(not match([Bill TO ID9,'value1','value2',valueN'),1,0) as _FlagNPValidBillTo or similar.

I don't like solutions where you have to alter the qvw for NP to work for most cases its better to either create a NP specific qvw or add NP specific fields to fulfil your reporting needs.

We will, in the hopefully not so distant future, have a reporting tool that can solve all needs without the need of alter the source documents.

In the best of worlds we could have filters on connections, evaluation criterias that returns multiple values and no limitations for source documents with triggers.

Br Johan

View solution in original post