#Database deadlock exception code#

In your catch block, your code can call Global::error to report the specific exception. These exceptions are not issued by a call to a method such as Global::error. Ensure Exceptions are DisplayedĮxceptions of type Exception::CLRError are not displayed in the Infolog. Your code can obtain a reference to the System.Exception instance by calling the CLRInterop::getLastException method. NET Framework System.Exception instance is thrown, your code can catch it by referencing Exception::CLRError. NET Framework classes and methods that reside in assemblies that are managed by the common language runtime (CLR). When you catch an exception that has not been displayed in the Infolog, call the Global::info function to display it.Įxception::CLRError, Exception::UpdateConflictNotRecovered, and system kernel exceptions are examples of exceptions that are not automatically displayed in the Infolog.įrom X++ you can call. Have an unqualified catch block at the end of your outermost catch list.Īvoid throwing an Exception enum value directly.ĭo throw the enum value that is returned from one of the following methods on the Global class (you have the option of omitting the implicit Global:: prefix):

Have a try block that contains all your statements in the outermost frame on the call stack. Therefore we recommended that you do all the following to provide effective exception handling: This means that an unhandled exception can be hard to diagnose. The system exception handler does not write to the Infolog. If no catch statement handles the exception, it is handled by the system exception handler. The retry statement erases messages that were written to the Infolog since program control entered the try block. The retry statement causes control to jump up to the first line of code in the associated try block. The retry statement can be written only in a catch block. This strategy is appropriate for the outermost try - catch blocks. This means it handles all exceptions that are not handled by a previous catch. One strategy is to have the last catch statement leave the exception type unspecified. It is common to have the first catch statement handle the Exception::Error enumeration value. The catch statements are processed in the same sequence that they appear in the X++ code. If the catch list has no block that specifies the particular exception, the system passes the exception to the catch list of the next innermost try block. If a catch is found that handles the kind of exception that is being thrown, program control jumps to that catch block. When an exception is thrown, it is first processed through the catch list of the innermost try block. For example, the Global::error method can be called simply as error('My message.'). In X++ code, the static methods on the Global class can be called without the Global:: prefix. You use the following X++ statements to generate and handle exceptions: It is common practice to write diagnostic information to the Infolog before throwing the exception, and the Global::error method is often the best way to do that. This exception is thrown in a variety of situations. A frequently thrown exception is Exception::error enumeration value. In X++, an exception is represented by a value of the enum named Exception. The instruction at which program execution resumes is determined by try - catch blocks and the type of exception that is thrown. What is an Exception?Īn exception is a regulated jump away from the regular sequence of program instruction execution.

You do not necessarily need to know the location of the catch block that will receive control when the exception is thrown. Your method can throw an exception to immediately transfer control to a catch code block that contains logic to handle this particular error situation. You can write your X++ code to handle errors by using the statements for generating and handling exceptions.įor example, your method might receive an input parameter value that is invalid.

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012