olisterr.tech | Blog on Dynamics 365 Business Apps, NAV / Business Central, Power Platform and Azure

Introduction: Now that NAV 2017 Database is upgraded to Business Central v14 (Refer link ), it's time to connect your AL Development with your Business Central environment. One of the issues with this approach is that NAV Database does not have the symbols generated. Pre- requisites : - Upgraded DB from NAV to BC - VS Code & AL Language Extension - finsql.exe - Business Central On-Premise with Windows Client Books & References: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-running-cside-and-al-side-by-side https://olisterr.blogspot.com/2020/04/resolving-tenant-default-is-not.html Demonstration: 1. Connect VS Code to Business Central Database: - Ensure that in Business Central Administration > Development > Enable Development Service Endpoint and Enable Debugging and Enable loading application symbol references at startup. Enable Development in Business Central Administration  - Ensure that the launch.json file in your project...

 Introduction: Now that the first step of the problem preprocessing of the NAV Database to make it ready to be migrated to BC is done(refer Part 1 ), we can now proceed further with connecting the database in Business Central On-Premise. Pre- requisites : Microsoft Dynamics 365 Business Central Microsoft Dynamics for NAV Microsoft SQL Server Management Studio (SSMS) Powershell ISE Understand NAV to BC Upgrade Considerations -  Click here Understand Upgrade Path -  Click here Books & References: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-considerations#online https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-paths https://www.sauravdhyani.com/2018/10/msdyn365bc-data-upgrade-to-microsoft.html https://olisterr.blogspot.com/2022/03/how-to-upgrade-data-from-microsoft.html https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-permissions Demonstration: 1. Ins...

Introduction: Imagine a scenario where as per the requirements provided by your clients, you have set up the Database structure in NAV/Business Central. Then comes a requirement in Phase 2 which completely redefines the database structure which was provided by you and you need to delete a few fields in a table and move it to another table. Pre-requisites: Microsoft Dynamics NAV Microsoft Dynamics Business Central Books & References: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-obsoletestate-property Solution: 1. In Microsoft Dynamics NAV, there was a flexibility to delete fields, tables, and keys and using  Force-Sync, you can directly delete the field, table, and keys from SQL Database. 2. Whereas in Microsoft Dynamics Business Central, you cannot delete the fields, keys, and tables. In order to deploy this deleted change, you need to mention this field, table, and keys with Obsolete State Removed. ...