QlikView 12.60 Reports within Qlik are "blown-up" when printing from Access Point

[njmaehler]

I am looking for a solution for one of my customers who recently "upgraded" from QLIKVIEW 11.20 SR12 to 12.60
Previously the client used IIS but this version decided to go with Web Server with this new upgrade - I say upgrade but actually it was a new installation on a new server however we took all the models designed in 11.20 and just opened them in 12.60 to look for any discrepancies.

Basically, in design mode everything on the Report preview looks correct but when you take the model to the Access Point portal then the objects are all resizing themselves and the font appears to be too big and some of the charts do not even scale with the "fill to aspect" option selected. This is all within the Report option found within QlikView itself. It is NOT NPrinting reports. 

The User Settings on Export tab - clipboard zoom is 100% on the server under the user properties.

Can you advise if this is a known issue or what we should look at? Has anyone seen this and can advise us? 

I looked at the following post but this is related to NPrinting however the reports I am talking about are just the Report menu option from within side QlikView itself. 
https://community.qlik.com/t5/Qlik-NPrinting-Discussions/Objects-rendered-in-PDF-suddenly-blown-up/t...

[marcus_sommer]

The normal view within the desktop client and also the IE plugin control the rendering itself - using mostly the libraries and API's from the OS to communicate with the graphic-card.

By using the AJAX client it's different. Here happens the whole rendering within the web-server and those transferred everything to the browser which may display it 1:1 or applying various adjustments - because of the used release and the supported features as well as the various default + customized user settings.

Without a more detailed idea what within the change between the old and the new environment could have such an impact it will be quite hard to find the real cause of the issue. Quite important will be to reduce the research on not working respectively changing things - means especially to ask the right questions, like:

• do the positions of the objects change
• is the object-size different
• what happens with borders and scrollbars
• text and numbers - are all object-parts affected like title, label, legends and so on or only the table-cell content

The differences here between no changes, rather small changes without a negative impact and the problem-areas could give good hints to the real cause. If I interpret the descriptions here right the cause could be related to padding/margin-settings in combination with the scaling/zoom-settings.

If there are quite experienced web-developer within your team it shouldn't be too difficult to find the reason - if not it's more painful. In this case I suggest more classical approaches within the trouble-shooting and applying an excluding- and/or comparison-approach. This means for example:

• creating a new app in the new environment with some simple test-data and test-objects
• moving this app into the old environment
• adding new objects within an old app and also comparing them in both environments
• taking a look on the html source-code from the apps to find any differences (here it would be very useful to have a very simple app - maybe just a single object)
• similar things

Good luck.

- Marcus

[Chip_Matejowsky]

Hi @njmaehler,

There are a couple of open investigations open with R&D about potential defects currently about this topic.  Suggest that you contact Qlik Support and create a case.  Thanks!

Best Regards

[njmaehler]

Just to keep you informed, we have logged a case with Qlik and are waiting for their response. 
Thank you everyone for your suggestions, we have tried them but not getting any joy.
We have noticed that it appears to be limited to the straight table and pivot table and the scatter chart. 

[njmaehler]

Another update: we have had a meeting with the Qlik support team and have managed to establish that this is definitely a bug in QlikView 12.60. This is not an issue in QV12.50 or QV12.40. We tested it in these various environments and both worked as per design (and as per our expectation from QV11.20). 

The way forward is that Qlik are going to submit these findings to their R&D department as a bug. 
We can choose to wait to hear back from them to understand turn around times or potentially we can decide to change our upgrade from QV12.60 to QV12.50 which they felt would not have an significant changes (holding thumbs because we have been testing for over a month due to the number of  models and the complexities there in).  We have chosen to wait a week or two for feedback before making any formal decision.

[njmaehler]

Hi Marcus,

Did did create a little test model and have tested it is various environments to track down where the issue was introduced. It appears to be only in QV12.60

[njmaehler]

Qlik have acknowledged it is a bug in QV12.60

[njmaehler]

Just an update to let you know that the QV12.60 SR1 has resolved this issue. 

[njmaehler]

Thanks for directing us to create the case. It has been resolved in QV 12.60 SR1 which was released on 21 September 2021.