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

Introduction: In Dynamics NAV Users Page, a SUPER User has the ability to add more specific user permissions to another user. However, while adding permission if the User mistakenly adds the company name to a SUPER Permission Set for all companies. This is actually a trap, as the user did not remove any permissions but only added by mistake and after adding this value, the data cannot be again set to BLANK. Pre- requisites : Understanding of NAV Powershell Module Microsoft Dynamics NAV Books & References: https://olisterr.blogspot.com/2021/03/setting-up-administrator-account-in-nav.html Demonstration: In my previous blog LINK , I discussed about a workaround to this issue using SQL and NAV Users pages. In this blog I will be sharing the steps to do the same using PowerShell Commands. Using the Powershell Command New-NAVServerUserPermissionSet -PermissionSetId SUPER -ServerInstance <ServerInstanceName> -WindowsAccount <WindowsUserName> Conclusion: Using the New-NAVUserPe

Problem Statement: Disclaimer:  This blog is only applicable for Business Central On-Premise Version. If you are stuck in the same issue, try this at your own risk.  I had installed  Business Central v14 (Spring 2019) On-Premise with LS Retail . In this, Business Central comes with a ready made setup to connect with VS Code. As I restored the DB given by LS Retail, I could no longer connect to VS Code. This could be a potential case of  Running C/SIDE and AL Side-by-side  or customising on top of LS Retail. Despite all the configurations being correct in project's app.json and launch.json, I could no longer connect to Business Central, I  couldn't download any Symbols  and I  couldn't publish any Extension  to Business Central.   App.json and Launch.json I checked all BC Administration setup for Development and it seemed to be perfectly fine. I had  Enabled Development Endpoint ,   Development Endpoint Port was 7049 ,  Target was set to Internal ,  Ena

Introduction: Azure DevOps is a very handy tool to manage project tasks, milestones, bugs, and documentation. But it is not just limited to that, it can also be used to manage all your deployments and building pipelines to manage your deployments. Lets take a look how to do this and how we can setup our repository to make auto deployments. Pre-requisites: VS Code Microsoft Dynamics NAV / Business Central Azure DevOps Subscription Understanding of  Version Source Control System like Github or TFS Understanding of PowerShell Books & References: https://freddysblog.com/category/ci-cd/ https://www.linkedin.com/pulse/cicd-business-central-nav-using-azure-dev-ops-dennis-fredborg/ https://github.com/olisterr/Webinars-Seminars/blob/master/365Saturday_Presentation_CICD_7-12-2019.pptx https://www.yammer.com/dynamicsnavdev/threads/414438668279808 https://github.com/olisterr/CI-CD- https://aka.ms/cicdhol Demonstration: 1. Creation of Azure DevOps Repository: Creation

Introduction: While Business Central upgrades from Version 14 to Version 15, there are few deprecation and additions done by Microsoft to the Base Application. These deprecation are good in terms of getting better systems as it upgrades. The drawbacks of Deprecation is that your App needs to be upgraded as well as it use BaseApp as reference. Additionally, additions done are good but when you Extension App clashes with Upgraded Base App. Let us discuss. Pre-requisites: Microsoft Dynamics Business Central Understanding of Business Central PowerShell Module. Books & References: https://www.yammer.com/dynamicsnavdev/threads/503231829262336?message_id=503231829262336 https://community.dynamics.com/business/f/dynamics-365-business-central-forum/377346/error-in-app-deployment-in-business-central-v15 Demonstration: While I was creating Extension App, I had added a field in Table Extension of BaseApp Tables when Business Central was on Version 13. Everything was fi

Introduction: Working with failed Scheduled Jobs can be a tiresome process. This is exactly the case where one of my client has an Invoicing & Payment Jobs which run once a day and Job Queue Entries fail to trigger these Jobs. No Errors in the Logs, No Execution Entry, Simply No Way of Figuring it out as to why Job didn't trigger. Contacting Microsoft Support, they are asking to simply Upgrade the Application to latest version. Which is not a preferred option as the database size is around 200GB. Let's see how to resolve this in a smarter way. Pre-requisites: Microsoft Windows Task Scheduler Microsoft Windows Powershell Microsoft Dynamics NAV(Administration Module for PowerShell & Development Environment) Books & References: https://docs.microsoft.com/en-us/powershell/module/microsoft.dynamics.nav.management/?view=businesscentral-ps Demonstration: 1. Building Objects to Run through a Codeunit: As you know that Job Queue Entries support Reports and C

Introduction: While I was testing InterCompany Setup, I faced an issue probably a limitation of the CRONUS standard license which comes with standard NAV/ BC On-Premise installations. Whenever I created new multiple Companies in NAV, I got an error ' Your program License doesn't permit support maximum N non-demonstration companies '. Pre-requisites: Microsoft Dynamics NAV 2018. Microsoft Dynamics 365 Business Central. Solution: I faced this error when I restarted NAV Client after creating a non-evaluation company. Thus, I cannot remove the company from front-end. I tried using Microsoft Documentation and found that it was actually possible (YAY!! 😁). Refer  https://docs.microsoft.com/en-us/dynamics-nav/how-to--delete-companies . Instead, it kept ruining things more. The Server Instance would stop without any errors and NAV Windows Client would infinitely work trying to connect to the workspace. Finally, I found that using Windows Powershell with NAV Manag