This article describes why a filter may not work with 'value is' as value type where filter value 'appears' to be 'text' when in actuality the use of a 'dual' in the data model results in the 'text' appearance of dimension values but are actually 'numeric' values.
Root Cause: Task values filter selection "YES" for Text value may not be representive for TEXT it could also represent as a NUM value
Resolution: Despite Nprinting caching the value in what appears to be a string the actual field value in Qlik was stored as a dual and Nprinting was only seeing the numeric representation of that value when executing the report. The report would run and complete but fail to apply ANY of the filter selections, not just those with the wrong value type. Changing the dual fields to numeric value on the Nprinting side solved the issue.References from R&D (Jira cases):
https://jira.qlikdev.com/browse/OP-2383 (A filter has to be created as "numerical values is", even if the cache shows string values. This works as design
https://jira.qlikdev.com/browse/OP-4933 (The text representation of dual field can not be used as a filter given how NPrinting currently applies filters. Filters must be based on the numeric [and non-ambiguous] value of the field