NPrinting Template Editor locks up with Processing message when previewing as XLSX
Using version "February 2025 SR1" although I didn't see that in the topic selection so I picked the 2024 version.
I have created a new NPrinting report, clicked Edit Template, and added a simple level and table. I can Preview as XLSX if there are only a handful of rows, but once I try to Preview with a large amount of data (like 300 rows, which is still only about 10% of the anticipated size), the Preview locks up with a Processing message. It does not time out or produce an error, and I usually abort after 30 minutes or so. Our internal support team does not see an issue on the server. Once I have this issue, the Preview locks up on even the small dataset again. They restarted all the services earlier in the week, and it worked again on the very small number of rows. Is it the case that the XLSX preview can't handle much data? I'm not sure how to continue developing the report without being able to preview with realistic data.
No, something is wrong and we just don't know what. Excel preview should work also on large data set as long as your Qlik Server can handle it and output can actually be produced in timely manner. Even if it takes long time you should see timeout error instead of no error.
Steps to validate and make sure they meet criteria.
Version of Qlik Sense
Version of NPrinting designer, server and engine - all MUST be on the same version!
Excel - is it plain vanilla excel or do you have corporate add-ins which interrupt often excel processes. For example law firms often have additional software installed to maintain their files which was notoriously annoying when working in designer as it was breaking it and creating non-responsive file
Are you working from office stable network?
Is your Qlik app supported (does not have any unsupported objects like "always one selected values etc"
Are you able to try this on different computer, maybe someone else in the team has another computer with working designer?
What are the specs of NPrinting server - just trying to understand overall performance vs minimum requirements
What is your template like?
(levels + individual columns as tables)
or levels with some charts/images?
just give us an idea what is the number of loops and iterations NPrinting will need to do to produce your outcome
cheers
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.
No, something is wrong and we just don't know what. Excel preview should work also on large data set as long as your Qlik Server can handle it and output can actually be produced in timely manner. Even if it takes long time you should see timeout error instead of no error.
Steps to validate and make sure they meet criteria.
Version of Qlik Sense
Version of NPrinting designer, server and engine - all MUST be on the same version!
Excel - is it plain vanilla excel or do you have corporate add-ins which interrupt often excel processes. For example law firms often have additional software installed to maintain their files which was notoriously annoying when working in designer as it was breaking it and creating non-responsive file
Are you working from office stable network?
Is your Qlik app supported (does not have any unsupported objects like "always one selected values etc"
Are you able to try this on different computer, maybe someone else in the team has another computer with working designer?
What are the specs of NPrinting server - just trying to understand overall performance vs minimum requirements
What is your template like?
(levels + individual columns as tables)
or levels with some charts/images?
just give us an idea what is the number of loops and iterations NPrinting will need to do to produce your outcome
cheers
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.
With a little more trial and error, I believe this may be related to whether the "Apply Sense app theme" is checked. I have had better luck now that it's unchecked, and I'm finding that the Cache Status locks up at Pending if I try to re-check the box in order to try again. For now, I am going to move on and assume that's the issue.
