From the Microsoft Dynamics NAV Blogs: Extensions 2.0; Account schedules; Web services connection refused; Batch name disappears

From this week's Microsoft Dynamics NAV blogs:

• Extensions 2.0 - Dynamics NAV 2018
• Create financial reports on the fly - NAV account schedules
• Connection refused error on NAV when connecting to web services
• Batch name disappears after you customize the journal page

Extensions 2.0 - Dynamics NAV 2018

On KSD Consultancy's Microsoft Dynamics Navision (Tips & Tricks) blog, Ashwini Tripathi provides a quick tutorial of using Extensions. Tripathi wrote that it's difficult to upgrade a solution from one version to the next when changes have been made to the underlying application, a problem which Extensions, and the new Extensions 2.0, solves:

Instead of defining customizations in the original source code, extensions are written alongside the solution source, where the integration with the source is handled with events. An extension can add new objects and extend existing objects that are present in the solution.

Tripathi wrote that the Extension code is packaged in a file that you can deploy to your solution, allowing you to upgrade the underlying solution. And as long as the events remain, the Extension will behave in the same way from one version to the next.

You can use the new developer tools to build, test, and deploy extensions so you can develop solutions for this new programming pattern, he wrote.

You can read more about it here.

Create financial reports on the fly - NAV account schedules

On the Fenwick Software blog, Ruby Usman wrote that Dynamics NAV offers a very efficient tool called "Account Schedule" that allows ...