It's taking so much time or sometimes freeze when i use Excel report from Designer.
I do the following report:
This actually works, but takes about 10-15 minutes to go... It's so long.
And if i put some other sums in report it works, works, works and then i got message like making report is taking more then 10 minutes try using task. In task it works for 1 hour and there is no result anyway.
So why NPrinting Excel reports working so long time?
Performance of NPrinting designe may depend highly on number of records in Qlik application. How big is your fact table / your Qlik app you are using to build this report.
As a good practice it is worth to have a small copy of the application to speed up design process in NPrinitng designer. On the other hand you are saying that your task is also failing. Looks like you are producing huge report on 2 different levels - do you (it is hard to tell as it is in your language)?
There is few questions you can ask right away and get quite straight forward answer:
how big is a source data (Qlik Application), how complex is your data model? Do you have star schema?
how responsive is Qlik Application - is it snappy? or slow and takes time to calculate every time you click on something. Report generation performance will highly depend on your Qlik Sense server performance
did you check Monitoring apps in Qlik sense when you are using NPrinting - see how CPU and RAM usage looks like
do you have supported configuration - NPrinitng on dedicated machine (different than Qlik Sense?)
how can you improve your expressions to calculate faster? is there anything you could improve in data model or expressions which speed up expression calc time?
Does your report (the excel you are trying to produce) fit in single sheet? Is NPrinitng server able to create such big file (I assume it can be quite big if it times out)
this is just starting point. It would be great to know the answers to your questions
cheers Lech When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please LIKE threads if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem.