Hi John,
Minimised objects are not taking CPU and RAM when Sheet is accessed by NPrinitng so the "access time" is shortened significantly (to be more precise if you had a caption in minimised chart which includes formula and calculates something than it will take up little bit of CPU & RAM, but still significantly less than fully visible objects.
You can test this by building big Pivot table in QlikView which can take say 10 seconds to calculate and check how your qlikview will behave when you access sheet where this object sits when maximized and when minimized. You will notice that maximized object will sort of prevent you from doing anything on the sheet untill pivot table is calculated.
Taking this approach to NPrinitng having minimized objects speeds up process of applying filters (also calculationg time consuming expressions (especialy when you are using levels in your NPrinitng), moving between sheets etc and therefore speeds up whole process of report generation run.
The other best practicies you will find here:
QVW size limitations with NPrinting 17
cheers
Lech
---------------------------------------------
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.
cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
