Suggest an Idea

[carlcimino]

Hello It would be extremely helpful to expose more errors to variables that users can utilize to help troubleshoot.

https://help.qlik.com/en-US/sense/February2022/Subsystems/Hub/Content/Sense_Hub/Scripting/ErrorVaria...

A common example is in the screen print below.   The script window shows an error occurs and then shows what the error is.  Would be great to have that highlighted line put into a variable in addition to having the error type (field missing).

https://help.qlik.com/en-US/sense/February2022/Subsystems/Hub/Content/Sense_Hub/Scripting/ErrorVaria... 

So it would appear here:

[simonaubert]

Hello,

Even more interesting : you can then script different actions according to the error message : retry or fail.

Best regards,

Simon

[carlcimino]

Hi @simonaubert , Yes that is part of the goal with using Call Try and Call Catch.  The other part is sending emails directly to the developer/app owner with the error message instead of going to the qmc and downloading the log.  The email would show the error type (field missing) and then the field that is missing which is the critical piece of info to solve for the error.

Happy Qlikking!

Carl

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.