Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I have a NP Task that generate an email with a date inside the subject. When it is scheduled to run within NP it ran successfully with the date
However if the same task was called from QS through NP API then it run successfully but the date was not evaluated
Appreciate any suggestion on how to resolve this.
Hi,
Could you share screenshots of the email configuration in the publish task? Did you insert the formula in the object directly? Did you try to create a variable in the source app with the formula inside and use it in the subject? Did you try to force the output of the formula in the text format by adding =Text(...formula...)?
Best Regards,
Ruggero
Hi,
Could you share screenshots of the email configuration in the publish task? Did you insert the formula in the object directly? Did you try to create a variable in the source app with the formula inside and use it in the subject? Did you try to force the output of the formula in the text format by adding =Text(...formula...)?
Best Regards,
Ruggero
Thanks Ruggero
Screenshot of the email configuration in the publish task
Its referencing the variable report_date_time which is used to insert into the subject %%Variable_User_FD_Exception_report_date_time%%
I have tried to force the output of the formula by adding the text in front of the formula
Hi,
I tested in Qlik NPrinting May 2022 SR4. I created a publish task with a variable in the subject created with the same syntax as yours. I ran the task via Web Console and via API call and in both cases, as expected, the subject of the delivered email is correctly filled with the date. I'm not able to reproduce the issue.
Check that the API call has the correct task ID. I have no other idea. You could open a support ticket with everything we need to reproduce, including the Qlik Sense app and a link to this conversation. Based on my tests the feature is working as expected.
Best Regards,
Ruggero
Customer confirmed it is working now for both Web Console and API call. Thanks @Ruggero_Piccoli