Let’s kick off with the Automated Testing on Microsoft D365 Business Central. If you are going to publish your app on Business Central, there are list of things you must complete before submitting it for validation. The checklist is available here (https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-checklist-submission).
One of the showcase features of Dynamics 365 Business Central is the ability to use the product within Microsoft Outlook clients using Outlook add-ins. There are two add-ins that come out of the box with Dynamics 365 Business Central: The Contact Insights add-in and the Document View add-in.
For almost 10 years, you might have become used to finding content online for Dynamics NAV in the MSDN Library. We announced last year that we’re moving to the Docs.microsoft.com site, and today we moved the last bits to the Docs site as well.
Online content for Microsoft Dynamics NAV 2016 and earlier versions of Dynamics NAV is now available in the Previous Versions section of the Docs site.
In Business Central running the Microsoft cloud we operate with three different object ranges in terms of licensing. Developing for Business Central is done using Visual Studio Code with the AL Language extension. Developing for Dynamics NAV can be done either by using Visual Studio Code with the AL Language extension or by using C/SIDE with an appropriate license file.
If you want to try the new Dynamics 365 Business Central please login into https://trials.dynamics.com/, and you just need to provide your work email address and Phone No.
If you already have signed up previously then, on login it will redirect you to the Finance and Operations Business Edition and to reset to Business Central you need to follow the below steps
With this blog post, Microsoft announced the March update of the Developer Preview. The usual Docker images will be publicly available on April 2nd and will contain the Microsoft Dynamics 365 Business Central release candidate.
In the blog post Microsoft listed a number of nice improvements and a lot of fixed issues. However, one of the improvements didn’t make it to the blog post, maybe because it was also discussed in one of the issues on GitHub.
Anyway, it is an import feature, so I’m going to explain it here. The tableextension object has four new triggers: