Skip to main content


Showing posts with the label Change Company

Generate Number Series from one Company and use it in another company

Introduction: When dealing with Number Series where the Intercompany Documents are created automatically using the code, using standard number series generation Codeunits cause problems. In this blog, I'll be explaining why this issue is caused and how to resolve such issues. Pre-requisites: Microsoft Dynamics NAV / Business Central  VS Code  AL Language Extension Solution: Issue: Let's say I'm logged in as user of Company B. When I create Sales Order in current company, I need to create Purchase Order in target company say Company A. When I use the Number Series declared on Company B's Purchase and Payable Setup for Purchase Order, the system either gives an error that Number Series does not exist or number generated is out of sync as Number Series are stored on Per Company basis. This results in overlapping of next PO number to be generated. Cause of the Issue: NoSeriesManagement Codeunit 396 works only with the No. Series for the cu

Managing with Multiple Legal Entity Data in Microsoft Dynamics NAV / Business Central

Problem Statement: Well, my client is a Trader of Oils & Fatty Acids and has multiple legal entities to perform various sets of operation on the TRUCK-LOAD(a.k.a. Load). One legal entity creates the Load and schedules it, while another manages with the freight requirements. The information is not shared between both the legal entities. Thus, we need to store the data separately. Pre-requisites: For Microsoft Dynamics NAV: - C/Side Development Environment - Multiple legal entity(Company) setup For Microsoft Dynamics Business Central: - Visual Studio Code - AL Language Extension - Multiple legal entity(Company) setup Solution Design: 1. Create two Tables say LoadCompany1 and LoadCompany2 with same fields 2. Set DataPerCompany property is to TRUE on both the tables. 3. In NAV/ BC, there are common tables but the data into the tables are different. Thus, the system has to manage different version for a single table based on an entity that you're currently working o