Microsoft Dynamics NAV Customizations versus Dynamics​ 365 Business Central Extensions – Development

With the release of Dynamics 365 Business Central in October of 2018, Microsoft introduced a new concept for programming and development called an EXTENSION. In prior versions of Microsoft Dynamics NAV, a programmer would modify the course code directly for tables, pages, reports and code units. This would provide the local programmer with great flexibility to simply change the tables or other code elements to suit the needs of the local user.  The drawback of this approach was that the programmer had to manually merge code elements that changed from one version to another every time that Microsoft issues a new release. Also, if a user had installed other add-on modules by third-parties, their own programming may interfere with that code as well. As a result, upgrading from one Version of Dynamics NAV to another became rather complicated, time-consuming and expensive.

Microsoft decided that a new cloud-based product such as Business Central needed a new approach and published this tool with their release of Dynamics 365 Business Central. Instead of using a programming language called C/AL which modified the core system objects, we are now using a language simply called AL which is part of the Visual Studio Code. Instead of modifying the core objects, a programmer can use the new tools to create new objects which are related to the core objects but are stored in separated containers. The system would maintain the link between these two resources automatically and more importantly, present them as ONE resource to the user when needed. As an example:

MicrosoftDevelopment Explanation

As you can see the new approach will allow Microsoft to control their own core objects without being concerned about other developers work. Also, this approach allows you to bundle all your own programming and install it easily on a new instance of your system by simply importing the extension. If you are commercial developer, you can use this approach to create a marketable collection of code and sell it on the Microsoft AppSource marketplace, after review and approval by Microsoft. When Microsoft does release a new version of their product, they can quickly and easily determine if any of the extensions are in conflict with the new release. These conflicts can be detected and addressed by Microsoft and the programmers well before the new release are made available.

In summary, the new approach called Extensions, greatly reduces the headaches and manual labor a developer would have to go through to upgrade from one version fo Microsoft Business Central to another and it completely eliminates any issues with more frequently released hotfixes.

If you have any questions, please feel free to reach out to our NAV to Business Central upgrade team to discuss a conversion from one model to the other and how CBR Technology may be of assistance. Our development team specializes in the conversion of Dynamics NAV C/AL code to AL Code as an extension for Dynamics 365 Business Central. We can be reached at Tel. 855-227-0700 or via e-mail at


Year-End Closing Procedures for Microsoft Dynamics​ 365 Business Central (formerly know as NAV 2016, 2017, 2018)

Microsoft Dynamics 365 Business Central (formerly know as Dynamics NAV) has a three steps Fiscal Year End closing procedure. Once the closing procedure has been completed, you may still record new GL transaction into the closed Fiscal Year, however, and Profit & Loss items will cause you to re-close the Fiscal year to retained earnings. For assistance with this process, please feel free to contact our Consulting Team at Tel. (855) 227-0700 or via e-mail at .

Please note that this process cannot be reversed, so please be certain that you are ready to proceed. We typically recommend that you prepare a COPY of your production company file. Also, if this is the first time you are completing this process, you might want to test it in your Sandbox copy.

If you are using Dimensions in your setup, please make sure to complete the proper section of the “Close Income Statement” wizard in accordance with your setup.

  • Use the Accounting Periods Setup page to CLOSE the Fiscal Year
  • Use the “Close Income Statement” to prepare a GL Journal entry by Dimension (i.a.)
  • Post the General Ledger Journal Batch with the YE Closing Entries



Upgrade from Dynamics NAV 2015, 2016, 2017, 2018 to Dynamics 365 Business Central – License Issues and Development

When you sign up for a new Microsoft Dynamics 365 Business Central account today, the company only offers names user licenses (subscription) just like they are being used by Office365 and Azure. This applies to both their Microsoft hosted and their OnPrem solution.

If you purchased Dynamics NAV prior to 1/1/2019, you will most likely have a concurrent user license. Microsoft will allow you to change your license and upgrade to Business Central, providing you are current with your annual maintenance. The following license conversion Matrix will apply.

  • For Every FULL concurrent user license, Microsoft will issue 2 named user licenses
  • For every LIMITED concurrent user license, Microsoft will issue 1 named user license

In addition, if you had your Partner make changes to the Dynamics NAV system using the C/AL programming language, you will need to modify these customizations to run on Microsoft new platform called an EXTENSION written in AL Code. In the past, the C/AL was modifying the actual Microsoft programming with regards to tables, pages and other objects in the system. This would result in difficulties when upgrading from one version to the next as these modifications had to be merged into the new code. The new EXTENSION model provides for the separation of the customization code into a new object called an extension, which can then be loaded and unloaded freely and easily, just like an App on your Smartphone.

CBR Technology can assist your organization in upgrading from prior Versions of NAV by providing development resources that have the experience and know-how to handle this C/Al to AL Code conversion.

Please feel free to contact us at Tel. (855) 227-0700 or via e-mail at . Please ask for Christoph Riechert to discuss your particular project.

Dynamics 365 Business Central (NAV) Manufacturing Demo

This video is designed to give you an overview of the core functionality of the Microsoft Dynamics 365 BusinessCentral (formerly know as Dynamics NAV) manufacturing module (MRP). The video will cover key areas of the Production Bill of Materials, Routing Setup, Work Centers and Machine Centers as well as Production orders and scheduling. Based on this brief review, you will get a sense for the power and functions of this Microsoft solution and the viability of this system for your organization. Please feel free to contact our sales and consulting team at TEl. (855) 227-0700 with additional questions.


Business Central

D365 BC – Posting Date is not within your range Error

The Dynamics 365 Business Central (Dynamics NAV) product allows you to specify a range of dates within which you are allowed to post the General Ledger. For additional assistance with your implementation or maintenance of your Microsoft ERP system, please feel free to call us at Tel (714) 901-5740. Finance Departments use this feature to control their users and specify what range of dates are valid. Typically, these settings are modified frequently throughout the year. The eror you receive when posting outside the range is:


To correct this error, the user must have full access tot he General Ledger Setup window.

Once you are in the window, update the starting and ending dates as indicated.

D365 BC General Ledger Setup

In addition, D365 BC allows you to control each individuals posting date ranges in the USER SETUP window as well. If you leave these fields blank, the system will use the GL Setup. Otherwise, please note the following configuration options:

D365BC User Setup for PostingDates

ERP System Architecture of the Dynamics 365 Business Central Platform – Comparison

When evaluating ERP system in today’s environment, the traditional approach of comparing pure accounting features become less relevant. As a matter of fact, most ERP systems such as SAP, Oracle, EPICOR and Microsoft have no meaningful differentiation in the core accounting modules including General Ledger, Accounts Receivable, Account Payable, Inventory Control, Sales Order and Purchase Order processing. The real differentiators are non-accounting feature, functions and architectural differences which might prove to be much more important. For a detailed conversion about this approach, please feel free to reach out to our team directly at (855) 227-0700 or via e-mail at .

Server System Architecture

  • OnPremise Database Support
  • Single-Tennant Hosted Support (Private Cloud)
  • Hybrid Config (OnPrem-Cloud Sync)
  • Multi-Tennant Cloud-Based Server
  • Highly scalable Database with Clustering

Client Access

  • Web Client
  • PC Client (Windows Program)
  • iOS Native App
  • Android Native App

User Security & User Interface

  • Windows Authentication – On-Premise
  • Windows Authentication – Cloud-Directory (AAD)
  • ERP System Authentication (non-Windows OS)
  • Support for 2 Factor Authentication
  • State of the Art – Web 2.0+ – Browser Design
  • Ability to export all data to Excel

Workflow Management

  • Creation of new GL Accounts
  • Onboarding of Customer, Vendors, Items
  • Approval of Sales Transactions (Quotes, Orders, Returns, etc.)
  • Approval of Purchasing Transactions (Purchase Order, Purchase Returns)
  • Credit Limit check for Customer
  • Additional Custom Workflows (Defined by User)

System Integration Options and Accessibility

  • Publishing of Web Services (ODATA, SOAP) for ALL data Objects
  • Database Integration which enforces Business Logic

Business Intelligence

  • Full integration with Microsoft Power BI
  • Ability to interface with Industry Leading Reporting Tools (Crystal Reports, Jet Reports)

International Considerations

  • Ability to support different user languages on the same Database
  • Ability to support multiple languages for item Master Records
  • Ability to show languages specific forms for Customers
  • Ability to show languages specific forms for Vendors
  • Ability to conduct Inter-Company Transactions (GL,AR,AP,SO,PO)
  • FASB-52 compliant Multi-Currency Support

Customization and Extensibility

  • Ability to modify Pages and Database using an Upgradable Tool
  • Visual Studio based DEV tool for Advanced Customization
  • Ability to purchase add-ons from Web Store
  • Using Word to modify Marketing Documents (Layout)
  • Ability to support multiple document formats for different Customers
  • Rapid Application Development (RAD) with new Microsoft Power Apps



What are the differences between the Assembly Order Module & Manufacturing Module in Dynamics 365?

Whether products are assembled or manufactured, Dynamics 365 Business Central (formerly known as Dynamics NAV), provides very powerful industry specific capabilities that are crucial to each of the two. This post briefly describes the differences between each module.

Assembly Order Features

For organizations that quickly assemble products to sell to customers, assembly orders simply use components to complete finished inventory items. These are companies that supply products to their customers by combining components in simple processes without the need of manufacturing functionality. Dynamics 365 includes features to assemble items that integrate with existing features such as sales, planning, reservations, and warehousing. Assembly items are defined as sellable items that contain an assembly BOM. They are internal orders, just like production orders, used to manage the assembly process and connect the sales requirements with the involved warehouse activities.

Assembly orders differ from other order types due to the fact that they involve both output and consumption when posting. The header of an assembly order behaves similarly to that of a sales order line, while assembly order lines behave similarly to consumption journal lines.

To support a just-in-time inventory strategy and the ability to customize products to customer requests, assembly orders may be automatically created and linked as soon as the sales order line is created. The link between the sales demand and the assembly supply enables sales order processors to customize the assembly item on the fly, promise delivery dates according to component availability, and to post output and shipment of the assembled item directly from their sales order interface.

On one sales order line, you can sell a quantity that is available and must be picked from stock together with a quantity that must be assembled to the order. Certain rules exist to govern the distribution of such quantities to ensure that assemble-to-order quantities take priority over inventory quantities in partial shipping.

Special functionality exists to govern the shipping of assemble-to-order quantities. When an assemble-to-order quantity is ready to be shipped, the warehouse worker in charge posts an inventory pick for the sales order line(s) in question. This, in turn, creates an inventory movement for the components, posts the assembly output, and the sales order shipment. Dynamics 365 supports both assemble-to-order, and assemble-to-stock methods that determines when and how the assembly order is generated.

Manufacturing Specific Features

For manufacturing organizations, a few features are necessary to ensure inventories of materials and finished goods remain accurate during the manufacturing process when materials are used, but the product has not yet been completed.

  • Adding the ability to record manufacturing labor against specific production orders and routing steps.
  • Attaching a routing sheet which defines specific work centers or machines that are required to be utilized to complete a product.
  • Assigning a capacity to each machine and resource to utilize capacity planning time sheet labor sources used and for how long.
  • Ability to track quality measures against specific routing steps.

It is important that consumption journals are recorded to identify all raw materials that were used from the output journal while the output journal identifies all finished products that were manufactured. Dynamics 365 has the ability to record these two journals at different times to ensure that inventory is accurate. The ability to track work in progress accordingly is also vital to manufacturing companies, again to maintain accuracy in tracking expenses, materials, resources, and inventories.

We hope this information was helpful in addressing differences regarding the two modules. With any questions regarding Dynamics 365 and other Microsoft Software Solutions, please contact us at (855)-227-0700 or visit our website CBR Technology. Thank you.