Qlik NPrinting OnDemand Report takes long to produce while content is processed quickly

[David_Friend]

After a Qlik NPrinting OnDemand report (based on a Word template) is executed, the content production time can take longer than the content resolution. 

Example from the Qlik NPrinting log files:

As more selections are made, the time required for content production increases exponentially. Further review shows that the Word format template includes many variables (both inner and outer). During the content resolution phase, monitoring the admin plan shows work being sent to the engine(s), however during the content production plan the admin plan is empty, and the CPUs on the engine(s) do not show a high load.

Resolution

The behavior is in line with the way Qlik NPrinting is expected to work.

Address performance concerns at the template level by revising the report, such as splitting it into smaller chunks. 

If you require assistance with the redesign or reengineering of the template itself to improve performance, contact Professional Services. 

A future optimization to the Word authoring capability in Qlik NPrinting may be considered, however, the impact on this use case cannot be forecasted to be an improvement at this time. 

Cause

• Microsoft has an internal document tree structure that is used to manage document structure and content 
• Qlik NPrinting uses this internal document tree structure to insert resolved content requests from Qlik products (QV or QS) 
• When levels are inserted there is a need to search the Word document tree repeatedly to add the content 
• While the boolean level determines whether a section of the report is inserted - it does not eliminate the need for the search to take place in the document in case the content must be inserted  
• The larger the document tree, hence the longer the searches take and non-linear growth in report production time (regardless of content insertion).   

Internal Investigation ID(s) 

QB-20076

Environment

NPrinting May 2022 and above
QlikView or QlikSense
Microsoft Word Report

[amehta]

we are experiencing the same issue and got the same reply from QlikView.  were you able to solve this issue?we are exploring other options and tools

[Sonja_Bauernfeind]

Hello @amehta 

The behavior is in line with the way Qlik NPrinting is expected to work.

If you require assistance with the redesign or reengineering of the template itself to improve performance, contact Professional Services. 

All the best,
Sonja 

[amehta]

this has been fixed in nprinting 2023 SR2