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

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: 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 =

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe

Introduction: In this blog, I will be explaining how to set up Envestnet Yodlee Bank Feeds and perform Bank Account Reconciliation. Pre- requisites : Microsoft Dynamics 365 Business Central Envestnet Yodlee  Banks Feed Add-On  Demonstration: 1. Installing Envestnet Yodlee  Banks Feed Add-On: Goto the Marketplace App and install the Envestnet Yodlee App. 2. Setup Envestnet Yodlee Setup: Goto Envestnet Yodlee Setup and input Consumer Email and enable. After that run the Test Setup action which will set up the Consumer connection with Envestnet Yodlee App. If there are any errors while setting up the app such as the one below. "You cannot use the Envestnet Yodlee Bank Feeds Services on the demonstration company. Open another company and try again". To handle this error, goto Company Information and ensure that the copy doesn't have 'Demo' field set to true. Use Configuration Package to set it to false. 3. Setup Import Bank Statement Setup Goto Bank Import / Export se

Introduction: The story starts with one of our clients who want to have Jet Report installed along with Dynamics 365 Business Central. After procuring the licenses, the client realizes he needs to connect Jet Reports to his home PC as well which may cost an additional license cost since Jet Report uses O365/M365 and Device Details as well to register its client. This means that it is not totally remote like Business Central(SaaS). So we need something that has all the data in the center but can connect to O365 as well as re-activate once the user changes the devices. It would have been easier if the client connected his home PC with office Azure AD, transfer the logins and AD metadata but that's unethical to some IT policies.  So after nearly 2 weeks of back and forth, the jet team suggested using Jet Hub, and the caveat was only 5% of the companies who install Jet Reports choose this option due to its complexity.  Meanwhile, I lost my patience and interfered thinking " How ha