Solutions Corner

Best Practices for Microsoft Dynamics AX

In today's competitive global marketplace, the right tools can make all of the difference. As a robust business management solution, Dynamics AX can help your enterprise work more efficiently, maximize your productivity and enable your enterprise to respond rapidly to changes in the marketplace. And just as important as the selection of the tool is the selection of the partner. To guarantee successful integration, your new solution needs to be specified and implemented by a partner that understands your industry, and has a firm grasp on the business logic behind manufacturing and distribution companies.

When using the Microsoft Dynamics AX development environment, you should adhere to a set of best practices. The X++ compiler checks the code for best practice issues. These issues can result in best practice errors, warnings, or informational messages.

They are recommended for any Microsoft Dynamics AX partner or end user who is enhancing or customizing Microsoft Dynamics AX.

These best practices apply to the following:

  • Programming in the standard application
  • Certified solutions

When using the Microsoft Dynamics AX development environment, you should adhere to a set of best practices. The X++ compiler checks the code for best practice issues. These issues can result in a best practice message that is an error, warning, or informational. Best practice checks are recommended for any Microsoft Dynamics AX partner or end user who is enhancing or customizing Microsoft Dynamics AX. The following sections provide information about the best practice checks that were added for this release. For information about Microsoft Dynamics AX 4.0, see New Best Practices in Microsoft Dynamics AX 4.0.

Application Integration Framework
Best practice checks for Application Integration Framework (AIF) verify that the data object is synchronized with the underlying artifacts that were used to define the data object. The best practice check is for missing or extra methods in the data object. For more information, see Best Practices: Application Integration Framework.

List Pages
The goal of the best practice checks for list pages is to establish a common look and behavior for all list pages. The checks are run for new or modified list pages. For more information, see Best Practices: List Pages.

Performance
Best practice checks for performance were added regarding indexes, extended data types, minimizing remote procedure calls, and details of RunBase classes. For more information, see Best Practices: Performance Optimizations.

Security
A best practice check for security was added to alert you when a dangerous API was used and a review is required. For more information, see Best Practices: Avoiding Potential Security Issues.

Tables
Best practice checks were added to prevent problems that occur when objects are marked to be deleted but are not linked to a SysDeletedObjects configuration key and vice versa. For more information, see Best Practices: Tables.

Table Fields
A best practice check was added to verify that when an InventDimId field is added to a table, code for handling the field is also added to the Multisite Activation Wizard. For more information, see Best Practices: Table Fields.

Workflow
Best practice checks for workflow focus on the properties of workflow categories, templates, approvals, and tasks. The checks verify that the properties are correctly configured for execution. For more information, see Best Practices: Workflow.

XML Documentation
Best practice checks for XML documentation focus on the validity of the documentation provided. The checks verify that particular sections are included. For more information, see Best Practices: XML Documentation.