Skip to main content

Posts

Adding Users in Dynamics 365 Business Central On-Premise

Introduction: I'm sure with the dawn of Business Central Online, its been so easy to directly get users from Office 365 and the only part that you are remaining with is setting up User Permissions. After SSL & SSO is setup in Business Central On-Premise, the question comes as how to add Users and connect to Azure AD. To get how to setup SSL and SSO refer the links below SSL Setup -  https://olisterr.blogspot.com/2020/03/how-to-setup-navuserpassword-with-ssl.html SSO Setup -  https://olisterr.blogspot.com/2020/03/how-to-setup-single-sign-onsso-for.html Pre- requisites : Microsoft Dynamics Business Central On-Premise SSL Setup SSO Setup Understanding of  Office 365 Understanding of Azure AD Books & References: https://olisterr.blogspot.com/2020/03/how-to-setup-navuserpassword-with-ssl.html https://olisterr.blogspot.com/2020/03/how-to-setup-single-sign-onsso-for.html Demonstration: For SSO Authentication -  1. Search for Users in Global Search and select the Users (Administrat

Update: Add User PermissionSet to NAV

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

Migrating Data from Business Central On-Premise to Business Central Online

Introduction: After the Business Central On-Premise is ready with the Customization and Data, it's time to migrate the Business Central On-Premise Environment to Business Central Online(Cloud). The end goal in mind is to migrate to Business Central Online(Cloud) Pre- requisites : - Microsoft Dynamics Business Central(On-Prem & Online) - SSMS - Microsoft Azure Data Factory Runtime - Basic understanding of SQL Server and Azure Data Factory Books & References: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/migrate-data Demonstration: 1. Setup SQL Server Authentication: Setup the SQL Server Authentication to SQL Server Authentication as follows. Enable Windows and SQL Server Authentication Mode Right Click on SQL Server Instance > Properties > Security > Server Authentication as SQL Server and Windows Authentication mode SQL Server Authentication Set to Windows and SQL Server Goto Security > Logins > <Username> > R

Enable AL and C/AL side by side for NAV Upgraded Database to Business Central

Introduction: Now that NAV 2017 Database is upgraded to Business Central v14 (Refer link ), it's time to connect your AL Development with your Business Central environment. One of the issues with this approach is that NAV Database does not have the symbols generated. Pre- requisites : - Upgraded DB from NAV to BC - VS Code & AL Language Extension - finsql.exe - Business Central On-Premise with Windows Client Books & References: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-running-cside-and-al-side-by-side https://olisterr.blogspot.com/2020/04/resolving-tenant-default-is-not.html Demonstration: 1. Connect VS Code to Business Central Database: - Ensure that in Business Central Administration > Development > Enable Development Service Endpoint and Enable Debugging and Enable loading application symbol references at startup. Enable Development in Business Central Administration  - Ensure that the launch.json file in your project