nPrinting Feb 2025 SR2 - Word Report Pivot Space Change

[ryan_byrne]

I recently upgraded nPrinting from February 2024 SR2 to February 2025 SR2. We also upgraded to Qlik Sense May 2025 SR6. After this point there seems to have been a change to the display of Word Reports using pivot table images. The vertical spacing seems to be much wider after the upgrade.

My observations are that it seems to be showing the same spacing in the new version as to when touch screen mode is turned ON in Qlik Sense. In the old version it seemed to use the same spacing as when touch screen mode is turned OFF.

The main issue is that the rows take up more space in the new chart and then less fits on the page.

I tried logging in as the nPrinting service account and changing to touch screen mode on the app, but this didn't seem to make a difference. I have created a dummy app and report and it shows the same behaviour.

Has anyone else come across this? Come up with a solution?

Old vs New: 

Dummy Report

[Lech_Miszkiewicz · Accepted solution]

Hi @Ruggero_Piccoli, @Frank_S , @Andrea_Bertazzo 

we have identified this issue and as @ryan_byrne  mentioned this seems to be behaviour due to mobile vs desktop screen rendering. In the past if your server/pc was not having touch screen by default you would end up having "touch screen mode" off. That was obviously default rendering also in NPrinting. Nowadays after upgrade it looks like "touch screen mode" stays on even if your device has no touch screen. I believe this is causing issue also for NPrinting as now it renders views in that mode by default which is causing discrepancies and truncates some data (not all rows are visible and scrollbar appear).

We have Qlik support ticket opened: 00407544: After upgrade the vertical spacing on an image pivot table is wider but for some reason it takes ages to get this across to R&D for review. Issue is simple, we can see what is causing it so lets get on with it and get a solution or issue bug fix ASAP. 

I am going on leave until 12th of Nov but I am sure @ryan_byrne will be able to assist you with this if you need more detail or explanation. I suggest you guys get someone on call with Ryan and he will be able to quickly explain it if need be. 

thanks for all your help, appreciate it.

regards

Lech

[Ruggero_Piccoli]

Hi @Lech_Miszkiewicz ,

Thanks, the support case is the best way to analyze this issue.

Best Regards,

Ruggero

[ryan_byrne · Accepted solution]

After a few weeks this issue seems to have gone away. Very strange, but can no longer replicate the issue.