Section Access will not solve your performance issue because nprinting authenticates a single time when opening the document using the service account or an specific user defined in the Connection.
Probably you have a design issue or with the data model or maybe in your report. I have a customer case with performance issue in report generation and the problem was in the report design.
If possible, share some details of report complexity and template used (pixel perfect, office template) and also the app size (number of rows on largest table for example).
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.
Thanks for your inputs.
I will share the details with you asap but till that can you confirm again in short:
Using section access for one user and Using filter in N printing for same field and value is same and switching to section access from N printing filtraion change nothing in execution time ?
AFAIK , if you have section access in your app no need to use filter untill unless you have perticular filter required.
without section access you need to use filters -- but if you use filter sometimes values and fields might have change so again you need to go to filters and adding evrymonth or frequently .
if you have section access it will give as it is even if you change the fields and filters also.