Extension Model: Creating a Static Table Method in Dynamics 365 for Operations

Creating table static methods for some tables was straight forward prior to the release of Microsoft Dynamics 365 for Operations (AX7), and arguably it still is if you are overlaying. Although this article is not intended to distinguish between over layering and extensions, I feel it is important enough to include some key points in this post.

Creating table methods that are static, while using the extension model are a little different. In this scenario, I will create a new method to validate that there is an entry in the external comment field in the table: TSTimeSheetLineWeek.

NOTE:  NOTE – I created a class with a name of the table (TsTimeSheetLineWeek) with the mandatory _Extension.

NOTE:  Parameter of static table method must be of the type of table you are creating the method for, in this case – TsTimeSheetLineWeek.

To call the method, you could do something like the following:

Over layering

A few key points to remember about over layering, include:

• You can customize source code and metadata of model elements that are shipped by Microsoft or third-party Microsoft partners.
• The overlaying model must belong to the same Package as the source model and belong to a layer that is higher than the source model.
• Over layering is a powerful tool to perform advanced customizations of metadata and source code, but may increase the cost of upgrading a solution to a new version.

Use of extensions

A few advantages to remember about the use of extensions include:

• Extension models simplify and improve the performance of deployments, builds, test automation and delivery to customers.
• Building your model or project doesn’t require you to recompile the entire application.
• Microsoft can install, patch, upgrade, and change internal APIs without affecting your customizations.
• Extensions reduce the cost of upgrading to a new version, as this approach eliminates costly code and metadata conflicts.