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

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