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

by | Updated June 13, 2017 | Development, Dynamics 365 for Finance and 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.

Related Posts

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Upcoming Events

june

02jun2:00 pm2:30 pmBusiness Intelligence for Batch Manufacturers

16jun10:00 am10:30 amHow AP automation can speed up month-end close in D365 Finance

17jun11:00 am12:00 pmConfab Live with Stoneridge – Real Time Marketing Strategies for Success

23jun10:00 am10:30 amThe Modern Manufacturer: Cost Accounting in D365

30jun10:00 am10:30 amAP Automation Checklist for a 2022 Rebound

30jun2:00 pm2:30 pmAchieving Success: How Technology Is Helping Nonprofits Thrive

july

01jul11:00 am12:00 pmConfab Live with Stoneridge – Dataverse Virtual Entities

14jul12:00 pm12:30 pmBeyond Reporting - What Business Intelligence Can Do For Your Agribusiness

15jul11:00 am12:00 pmConfab Live with Stoneridge – Integration Strategies for End User Success

21jul10:00 am10:30 amThe Modern Manufacturer: Manufacturing Software in the Real World

21jul12:00 pm1:00 pmIs it Worth it to Upgrade to Dynamics 365 Finance and Supply Chain Management? - Everything AX Users Need to Consider

About Stoneridge
Stoneridge Software is a unique Microsoft Gold Partner, with emphasis on partner. With specialties in Microsoft Dynamics 365, Microsoft Dynamics AX, Microsoft Dynamics NAV, Microsoft Dynamics GP and Microsoft Dynamics CRM, we focus on attracting the most knowledgeable experts in the field to our team, and prioritize delivering stellar solutions with maximum impact for your business. At Stoneridge, we are deeply committed to your results. Each engagement is met with a dedicated team, ready to provide thorough, tailored, and expert service. Based in Minnesota, we intentionally “step into your shoes,” wherever you are. We focus on what you care about, and develop trusting, long-term relationships with our clients.

Subscribe To Our Blog

Sign up to get periodic updates on the latest posts.

Thank you for subscribing!

X