I have set up two apps in nPrinting which connect to two seperate Qliksense apps. The connections generate fine and I create the reports which also preview fine then I have set up a task to output to a file system destination. This all works.
Sometimes the output is blank, no errors or anything just blank. I go in and preview the nPrinting report and its blank too so I regenerate the cache and then its fine and all works again.
Has anyone seen this behaviour?
We have nPrinting with Qlikview as well and this isn't somethign we've seen with that setup.
With respect, I don't need to read anything as we are not new users of nPrinting, we have another seperate instance of nPrinting connecting to Qlikview as opposed to Qliksense which is working fine for multiple report outputs and where we very rarely have any issues.
As I saw it isn't a case of this not working at all, if I regenerate the cache and then preview in nPrinting designer and then run my publish task I can see a file fully populated with data as expected.
Then sporadically, this exact same task with no changes other than the source app has been refreshed may run as expected or produce a file with no data in it.
Last night I edited and published the Qliksense app. I regenerated the cache, previewed the report, could see everything I expected and yet the publish task this morning after the QS App had been refreshed output 2 files of 8k with no data. I preview the report in nPrinting, no data. I regenerate the cache, preview the 2 reports, both are fine, I run the tasks, 2 files produced as expected with all data as expected.
I can't explain this behaviour as its not something I have seen before. I have had tasks fail and its normally cause files are locked out but this is really weird.
Are you using native Qlik Sense Straight Table? or PivotTable...
Also - Just to confirm, you are not using extension object /table like Vizlib or similar?
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.
Did you have task failures? Can you post the execution task errors and the log files?
If not I suggest you to open a support ticket with everything we need to reproduce the error (Sense app, template, steps, log files, etc).
Best Regards,
Ruggero
Best Regards, Ruggero --------------------------------------------- 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 with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
ok - I agree as you said above - this is strange and what you do is straight forward and should just work.
Moving forward I would suggest contact support as this is something what would require deep investigation, going through logs (NPrinting and Qlik Sense and both server logs).
@Ruggero_Piccoli - what do you think? Is this a case for support? From my point of view there is nothing else we can suggest. Weird thing is that regenerating metadata fixes the problem. As I said before, I saw similar behaviour with poorly designed apps and object, but as Phil said it does not take much time to open app and calculate object therefore I am not considering this to be a case.
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.
@Lech_Miszkiewicz we wrote the same at the same time! I think we can check the execution task page and log files error messages and no more. The to go ahead a support ticket with all the details is needed.
Best Regards,
Ruggero
Best Regards, Ruggero --------------------------------------------- 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 with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
the other objects i consider troublesome despite them not being listed as not supported.
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.
