Best Practices for Methods

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

Methods should:

• Be logical.

• Do a specific task.

• Have no side effects.

• Be well structured, especially when it comes to good places for overriding and for overlayering.

Make your methods small and logical. If you have a method that does more than one 'thing'; then consider splitting it up in two (or more) methods. It will then be easier to override or overlayer exactly the functionality that needs to be specialized or customized.

Do not have any unused variables in your methods.

For more detail about best practices for methods, see:

• Best Practices for Method Modifiers

• Best Practices for Local Functions

• Best Practices for Table Methods

• Naming Conventions: Methods

• Best Practices for Parameters

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