topic Re: Using Set Analysis to ignore filter not work in NPrinting in Qlik NPrinting

Using Set Analysis to ignore filter not work in NPrinting

rdelagarde — Wed, 23 Oct 2024 12:03:44 GMT

Hello,

Here is my dataset:

When I select ‘London’ and ‘Paris’ for the City field and I select ‘Alice’ for the Name field, this is what I get for my measurement in my Qlik Sens application:

Count({< Name= >} City) = 2
Concat({< Name= >} City) = London, Paris

However, when I export my NPrinting report with the same filters, this is what I get in my report:

Count({< Name= >} City) = 1
Concat({< Name= >} City) = London

I don't understand why the city ‘Paris’ disappears?

Thanks a lot!
Rémi

Re: Using Set Analysis to ignore filter not work in NPrinting

Frank_S — Wed, 23 Oct 2024 21:35:18 GMT

We are likely not seeing the entire picture here necessarily.

The potential impact of section access in your source app along with NPrinting user, report, publish task or table object level filters could be in play.

Check these to ensure that you are not having a filter conflict or section access that is causing the behavior that you are experiencing.

Further the use of 'Always one selected' in your app 'could' be interfering as well. Check your dimensions so that none of them use the always one selected property as these are not supported.

Unsupported Qlik Sense Object Support and L... - Qlik Community - 1717018

Finally, if your table or filter pain is a third party object, switch to native Qlik table and filter objects and try again. We have seen problems with third party objects but those are not supported by Qlik. When switching to supported native Qlik Objects, similar issues have been resolved.

Kind regards...

Re: Using Set Analysis to ignore filter not work in NPrinting

Lech_Miszkiewicz — Wed, 23 Oct 2024 21:47:49 GMT

Hi @rdelagarde

totally agree with @Frank_S on all his points, but also

we dont see your template
if you are trying to use levels, pages or cycles with set analysis it may not work for obvious reasons-those values are not in current selection state hence cannot be looped through.

i suggest you give us little bit more context of how you constructed your report an i am sure we will come to the bottom of this

cheers