As per NPrinting Documentation: Time = Time of day the report is generated. The format of the time can be selected from the drop-down list in the second field.
But when NPrinting trigger generates the report, it is always -1 hour from the actual time of the report generation. Means, if the trigger runs at 11:00, Report name will have 10:00. All my reports are having the same issue.
I hope someone can help me on this. I'm a newbie and not sure if this is the normal behavior of NPrinting or I am doing something wrong.
June 2018 is no more supported. I suggest you to upgrade to latest version (May 2021 SR2 at the moment I'm writing) because it could be an already solved issue.
For example February 2021 has the following issue solved:
Wrong date and time values in dynamic naming Date and time variables used in dynamic naming were incorrectly set to the same value if two recipients had different time zone settings, but identical filters applied. Date and time are now set to the task startup time, in the recipient time zone.
that is similar to the one you mentioned.
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.
Thanks for your reply. Update or upgrade seems remote right now in my workplace, is there a workaround on this? What I would like to do is append the timestamp that the report was generated or at least, the timestamp when the data was processed on the Qlik sense side may be?
I don't know a workaround. Maybe you can try to create a calculated field in the source app and use it in the dynamic name.
Next version May 2021 SR3 will be available soon (I don't know the exact release date) and if it will contain all planned issue fixes there will be also another fix related to this topic. You are running a 3 years old version no more supported so, if you will open a support ticket for example, the first answer will be: "Please upgrade to a supported version".
My suggestion is wait until next May 2021 SR3 will become general available and plan an upgrade to that latest version. Then please remember that we support a maximum of 2 years old version so I suggest you to plan a yearly upgrade to always run a supported version.
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.
