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

Introduction: While doing Data Migrations from BC14 to BC22, there was an error ' Invoke-NAV ApplicationDatabaseConversion: An unexpected error occurred after a database command was cancelled.' in Business Central in the Database Conversion. I confirmed the DB connectivity is working fine and failed only at Invoke-NAVApplicationDatabaseConversion. Pre-requisites: 1. Understanding of BC Data Migrations 2. Basic understanding of SQL versions Demonstration: As you know that while upgrading NAV / Business Central, you are requested to run the Application Database Conversion. In this case, I was directly trying to convert from BC14 to BC22 and I ended up with this error. To confirm this I checked the Upgrade compatibility matrix  https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-v14-v15-compatibility  and then there was an unexpected error. I tried to do the steps again and seem to receive the error again. After checking the Event Viewer it wa

Introduction:  There are times when Microsoft releases the latest major version upgrade for Business Central Upgrade and you face many issues with it. As soon as the bugs are reported to Microsoft, they start to fix them and ask you to upgrade to a certain Cumulative Update. In this blog, I will be sharing my experience with Business Central v21 CU0 upgrade to Business Central v21 CU2. Pre-requisites:  Business Central DVD for Latest CU Basic Understanding of Business Central CU Updates Books & References:  List of Update Packages How to Update CU version Demonstration:  1. Check the current state of BC: As part of knowing the current state of your Business Central environment, I'm assuming that your Business Central Environment will have some data in the standard Base App also there will be customization with extended tables and newly created tables. Customization - TableExtension on Customer Table  Customization - Custom Table created Make a note of the data that is present i

Introduction: Business Central Updates after updating to version 20.x, there is a common problem which is observed. The Business Central environment starts blinking as per the video below - Pre- requisites : Business Central Online  v20 Demonstration: 1. Restart the Business Central Environment: Go to Business Central Admin Center > Select the Environment >Sessions > Restart Environment. 2. Ensure that your URL contains Tenant ID: When you login into the Business Central Environment, make sure that your links are in the following formats Sandbox : https://businesscentral.dynamics.com/<SandboxEnvironmentName>/?sandbox=true Production : https://businesscentral.dynamics.com/<ProductionEnvironmentName>/ If you URL like https://businesscentral.dynamics.com/SandboxName or any other format without Tenant ID, chances are that you will end up with the issue. Also, you can login through Admin Center URL -  Connect from URL in BC Admin Center 3. Check the status if the insta

Introduction: When migrating from NAV 2017 to NAV 2018 i.e moving from C/AL to AL the created objects need not be created again from scratch in AL. This blog demonstrates how we can create the AL objects from C/AL using Txt2Al in Command Prompt. Pre-requisite: NAV 2018. Backup of Objects in TEXT or FOB format. Steps: 1. Import objects in NAV 2018 from the created  . TXT or . FOB files. In NAV Development Environment goto, Files > Import > Choose the .FOB or  .TXT file > Replace all the objects 2. Export the objects in New Syntax to . TXT files. Create a directory to store the objects in .TXT format which will be exported as new syntax. Here, ‘source’ is the name of the directory used. Use  ‘mkdir source ‘ Create a directory to store the .AL that will be created by TXT2AL Converter utility. Here ‘target’ is the name of the directory used. Use ‘mkdir target’ To export the objects in .TXT format in NewSyntax use the following command where Source Directory =