- Tue Nov 17, 2009 5:50 pm
#5042
I have an SQL insert statement in a trigger that fires after the final step in a task. I'm using executeQuery() to run the SQL.
If the insert fails for whatever reason, the use sees a generic red "Trigger Error" message, but still has the Continue button which will just derivate to next task/user as if there was no problem. I need some way to make the error a little more obvious, but more importantly to keep the user in the case (until they track down the error or call for support).
Do errors in triggers always "block"? The example code for executeQuery() shows several instances of tests to run after the function to see what happened. Are there best practices for dealing with serious errors in PM triggers?
If the insert fails for whatever reason, the use sees a generic red "Trigger Error" message, but still has the Continue button which will just derivate to next task/user as if there was no problem. I need some way to make the error a little more obvious, but more importantly to keep the user in the case (until they track down the error or call for support).
Do errors in triggers always "block"? The example code for executeQuery() shows several instances of tests to run after the function to see what happened. Are there best practices for dealing with serious errors in PM triggers?