Share via

Setting Development Options

  • Article

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

To set development options in Microsoft Dynamics AX click Tools > Options, and then click the Development link. The following table describes the options for development.

General

Description

Startup project

Specify the project to load at startup.

Message limit

Specify the maximum number of lines to save in the info window. When this limit is reached, the lines are discarded.

To view the discarded lines, you can examine the objects log file in the systems main directory. Log files are called <first four letters from object>comp.log, for example Bankcomp.log for the log file that results from a compile of the object called BankAccountReconcile.

These log files are temporary and the file names are not unique.

The log file in the above example is overwritten when you next compile an object called, for example, BankDepositSlip.

Development warnings

Specify whether to view development warnings in the message window during X++ code translation.

A warning is displayed if, for example, there are SQL statements that may result in inferior performance. The following SQL statements result in a warning if a key does not exist on the table myTable with the fields myField1 and myField2:

select * from myTable where myTable.myField1==x && myTable.myField2==y;

Startup model

Specify the model to load at startup.

Execute business operations in CIL

Specify whether to execute business operations in the code interop layer.

Application object tree

 Description

Application object layer

Specify the layer view on elements in the tree.

  • Show no layers – no objects are labeled with layer indications.

  • Show all layers – all objects are labeled with layer indications for all layers in which they exist.

  • Show highest layer – all objects are labeled with a layer indication for the highest layer.

  • Show corrected layers – only objects that have been modified in the current layer or a higher one are labeled and only with an indication for the highest layer.

  • Show all from corrected layers – only objects that have been modified in the current layer or a higher one are labeled but with indications for all layers.

To learn about application object layers, see Layers.

Application object model

Specify the model view on elements in the tree.

  • Show no models – no model information is appended to element names.

  • Show on all elements – model information is displayed on all elements.

  • Show on elements in current layer only – model information is displayed only on elements that exist in the current layer.

  • Show on elements in current model only – model information is displayed only on elements that exist in the current model.

To learn about application object layers, see Layers.

Debug

Description

Debug mode

Use the Debug mode list to define when the debugger is activated.

  • No: debugger is never activated.

  • When Breakpoint: debugger is activated when a breakpoint in the X++ code is encountered.

Auto

Description

Auto-update

Type the number of seconds of keyboard inactivity before the system should initiate a new update cycle.

A value of 0 (zero) disables the systems update cycle.

Auto-refresh

Select this if you want the system to update elements automatically so that elements that are made by other users become available to all users. In addition, the system updates lock indications in the Application Object Tree (AOT).

You can also refresh manually by using the Refresh command in the shortcut menu, for example on the Forms or the Queries nodes.

Note

Refresh is one of the three components in an update cycle, and is performed only when an update cycle interval is specified (the Auto-Update option).

Auto-save

Select this if you want the system to save elements automatically. When the Auto-Save option is enabled, the system automatically saves the unsaved objects when you exit.

Note

Automatic save is one of the three components in an update cycle, and is performed only when an update cycle interval is specified (the Auto-Update option).

Garbage collection limit

Specify the number of open elements before garbage collection is made.

The system uses memory each time an element is opened in the AOT. Unless a value is specified here, elements are never discarded from memory.

  • An element is considered open when:

    • The element node is expanded in the AOT, or

    • A method is open in the X++ editor, or

    • The properties are displayed, or

    • The element is displayed in the visual form editor or in the visual report editor, or

    • The element has been changed but not yet saved.

Note

Garbage collection is one of the three components in an update cycle, and is performed only when an update cycle interval is specified (the Auto-Update option).

Trace

Description

Database trace

Select this if you want the system to trace to the message window whenever the database is accessed.

Client/Server trace

Select this if you want to include information about where classes are executed.

ActiveX trace

Select this to enable tracing of ActiveX control events.

This means that all events that are fired by the ActiveX controls are logged in the message window. Different ActiveX controls fire different events, but most ActiveX controls share a common set of events, such as MouseMove, MouseDown, MouseUp, KeyDown, KeyUp, and so on.

Property sheet

Description

Sort alphabetically

Select this option to have properties sorted alphabetically when they are displayed in the property editor.

Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. Get your copy at the MS Press Store.