Nprinting PixelPerfect unexpected filter behaviour

[escayolaj]

I am using Nprinting 17 (February 18 version) with a QlikSense connection.

I have created a very simple app with a very simple table as such:

In Nprinting I have created a report with the table above imported as level and added in a detail report:

Then I applied the following filter:

Assuming that filters in Nprinting work as filters in QlikSense (selections), I would expect the outcome to be similar to the first screenshot due to the set analysis of the second expression. However, the outcome is:

Am I missing something? Is this behavior intended? Is this a bug?

Has someone else experienced this?

It looks to me like a very noticeable bug.

Thank you for your help.

[Daniel_Jenkins · Accepted solution]

Hi Jose,

This works fine in other report types that I tried - the issue is manifest with PixelPerfect only (as far as I can tell). Not sure if it is because of the Levels & detail report created in PixelPerfect that is not required in other formats.

Here is a test result with HTML (I added a formula to display current selections on Dim1 - GetFieldSelections(Dim1) - this too does not evaluate in PixelPerfect).

This could be a limitation in PixelPerfect because of the different way reports are created. I suggest you open a case with Support so it can be investigated further.

HTH - Daniel.

[escayolaj]

Thank you for your reply Daniel.

[escayolaj]

For other users, in some cases this bug will raise the error "Wrong content node response type".

[Ruggero_Piccoli]

Hi,

I think "Wrong content node response type" is not related with the filter issue. Please upgrade your installation to latest version of Qlik NPrinting and try with it. If the issue remains open a support ticket because it needs a deeper investigation that is not possible to do via community messages.

Best Regards,

Ruggero

---------------------------------------------

When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.