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

 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. Install Business

Introduction: The launch of the Microsoft Dynamics Business Central gave way to upgrades from Microsoft Dynamics NAV to Microsoft Dynamics Business Central. This blog is about sharing my experiences with Business Central Upgrade from NAV 2017. However, for different versions of NAV, a set of steps are to be followed to get to NAV 2017 and then upgrade to 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 Demonstration: Microsoft Dynamics NAV to Microsoft Dynamics 365 B

Introduction: Today, I received a call from one of the NAV Administrators stating the issue as if I try to access the User Card page for some users I receive the following error. Upon investigating it was clear that the Administrator by mistake deleted his own access to the company for all the users who have access to a different company. Even using the Administrators account I cannot get access to a different company. The condition here was that I cannot simply clear all User Access as per the blog below. https://www.sauravdhyani.com/2012/12/you-are-not-authorized-to-sign-in.html Pre- requisites :  Microsoft Dynamics NAV / Business Central On-Premise Demonstration: 1. Modifying User using SQL Database: If observed it evident that whenever the Administrator account is added there should always be a Windows User associated with it. To remove this constraint, modify the Username in User Table and Windows Security ID using SSMS in SQL Tables. Changed the User Name to ADMINISTRATOR-1 and o

  Introduction: I have been working in NAV/BC for a couple of years to master the craft and to some extent all of us are successful. But a single scenario/ user error/misunderstanding can create a big question mark. This blog is mainly divided into two parts 1. Why does NAV/BC support few small things which are not supported when analyzing the data? 2. Workaround and its implications. So the use case is the NAV/BC Administrator creates an Item with the number in the 'ABC-1039-(A)'. He and other users do all the manufacturing, trading activities. When he tries to run reports having Item No. Lookup using Table Relation, he is given the following error. Pre- requisites : Microsoft Dynamics NAV / BC References: https://community.dynamics.com/nav/b/moxie4nav/posts/convert-setselectionfilter-to-setfilter Demonstration: 1. Checking if this scenario is supported by spinning up some test code. Turns out when I hard-code Item No in SETFILTER, the report is working precisely as expected.