You can modify the value of a variable by double-clicking the value. Each variable is associated with a client or server icon. If a variable is changed as you step through execution, it is marked in red. Global variables are variables on global classes that are always instantiated: Appl, Infolog, ClassFactory, and VersionControl. Local variables are variables in scope at the current execution point.
![morphx and the application object tree morphx and the application object tree](http://1.bp.blogspot.com/-e7NzxcBgCzQ/UKJGngxAInI/AAAAAAAAAD4/sqA4A1atnjo/w1200-h630-p-k-no-nu/CompanyInfo.jpg)
Shows local, global, and member variables, along with their names, values, and types. This pointer is particularly useful if the execution path isn’t what you expected or if you want to repeat a step. You can drag the next-statement pointer in the left margin. TABLE 2-6 Debugger user interface elements.Įach variable has a ScreenTip that reveals its value.
#MORPHX AND THE APPLICATION OBJECT TREE WINDOWS#
Table 2-6 describes the debugger’s various windows and some of its other features. Figure 2-17 shows the debugger opened to a breakpoint with all the windows enabled.įIGURE 2-17 Debugger with all windows enabled. You can control execution one step at a time while inspecting variables and other aspects of the code.
#MORPHX AND THE APPLICATION OBJECT TREE CODE#
The main window in the debugger initially shows the point in the code where a breakpoint was hit. This means that your breakpoints are not cleared when you close AX 2012 and that other AX 2012 components can access them and break where you want them to. Each developer has his or her own set of breakpoints. For a list of all breakpoints, press Shift+F9.īreakpoints are persisted in the SysBreakpoints and SysBreakpointLists database tables. To enable or disable a breakpoint, press Ctrl+F9. A breakpoint on the last brace will never be hit. If you set a breakpoint on a line without an X++ statement, however, the breakpoint will be triggered on the next X++ statement in the method. You can set a breakpoint on any line you want. Running the application with debug support enabled also noticeably affects performance. If you do, execution will stop when it hits a breakpoint, and the client will stop responding to users. It is recommended that you do not enable any of the debugging capabilities in a live environment. This is necessary to prohibit unauthorized debugging, which could expose sensitive data, provide a security risk, or impose unplanned service disruptions.
![morphx and the application object tree morphx and the application object tree](https://vbook.pub/img/crop/300x300/plon0r13j8w3.jpg)
This is normally ensured by using setup, but if you did not set up AX 2012 by using your current account, you need to do this manually through Edit Local Users And Groups in Windows Control Panel. For Enterprise Portal code that uses the BCPROXY context to run interpreted X++ code, in the Microsoft Dynamics AX Server Configuration Utility, create a new configuration, if necessary, and select the check box Enable Global Breakpoints.Įnsure that you are a member of the local Windows security group named Microsoft Dynamics AX Debugging Users.Create a new configuration, if necessary, and then select the check box Enable Breakpoints to debug X++ code running on this server. From the AOS, open the Microsoft Dynamics AX Server Configuration Utility under Start > Administrative Tools > Microsoft Dynamics AX 2012 Server Configuration.In the Development Workspace, on the Tools menu, click Options > Development > Debug, and then select When Breakpoint in the Debug Mode list.You must enable debugging for each component as follows: The debugger starts automatically when any component hits a breakpoint. You set breakpoints by using the X++ code editor in the Development Workspace. NET.” Enabling debuggingįor the debugger to start, a breakpoint must be hit when X++ code is executed. As a stand-alone application, the debugger allows you to debug X++ in any of the following AX 2012 components:įor other debugging scenarios, such as web services, Microsoft SQL Server Reporting Services (SSRS) reports, and Enterprise Portal web client, see Chapter 3, “AX 2012 and. The debugger is a stand-alone application, not part of the AX 2012 shell like the rest of the tools mentioned in this chapter. Like most development environments, MorphX features a debugger.