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

Introduction:  In this blog I will be discussing about Permission Sets as Objects and how they are different from Permission Sets in earlier versions of NAV/BC. Also, I will share some insights on my experience with Permission Sets. Pre-requisites:  Understanding of Permission Set Objects Understanding of how Permission Sets work. Books & References:  Permission Set Object Upgrade Permission Sets Demonstration:  1. Permission Set as Data: In earlier version of NAV / Business Central, the Permission Sets were stored as data. Meanwhile, you would get the Permission Sets configured as Data in your Database. Generally when you upgrade from NAV, you will get this data upgraded automatically. You  can import/export permission sets as XML files. 2. Permission Set as XML: For every PTE it is mandatory to have your own Permission Sets. We create these permission sets as XML files for Business Central PTEs. For rest of the Base Application, Microsoft had in database and can be exported as XM

  Introduction: In my previous blog , I discussed on what is Microsoft Dataverse and how to setup Dataverse Connectivity with Business Central. In this blog, I will be attempting to share my experience on fine-tuning various parameters  involved in Business Central integration to Dataverse provided in connector  Pre- requisites : Microsoft Dynamics 365 Business Central Microsoft Dataverse Basic understanding of Dataverse and Business Central Books & References: https://docs.microsoft.com/en-us/dynamics365/business-central/admin-how-to-set-up-a-dynamics-crm-connection Demonstration: 1. Dataverse Connection Setup: For any setups related to Dataverse Connectivity the first step is you go to Dataverse Connection Setup You search for Dataverse Connection Setup All the setups related to Dataverse Connection Setup are in the actions of the Dataverse Connection Setup 2.  Connection Actiongroup: The actions in the Connection Actiongroup are mentioned as follows - Assisted Setup  -  Takes yo

UPDATE: Business Central Sandbox Tile in Microsoft 365 will be removed! When I logged into Business Central, it occasionally shows me the warning that the Business Central Tile will be removed from Microsoft 365 Apps Tile as follows.  Before the change, there was separate tile for Business Central Sandbox and Business Central Production. After the change, there will be single tile for Business Central Sandbox and Business Central Production. Please note that this feature will be in effect from April 2022 and will be in General availability in June 2022. For more details, refer the Business Central Documentation link below. https://docs.microsoft.com/en-us/dynamics365-release-plan/2022wave1/smb/dynamics365-business-central/single-tile-go-business-central

Introduction: In one of my blog on Setting up OAuth Authentication for Webservices and APIs in Dynamics Business Central, I shared how to setup OAuth Authentication. With Dynamics 365 Business Central releasing version 20, the Webservice Key Authentication has become OBSOLETE and all your integrations are to be moved to OAuth Authentication. There are few more steps in addition to the steps I mentioned in the blog above and those will be seen in the demonstration. Pre- requisites : Microsoft Dynamics 365 Business Central Understanding OAuth Authentication Understanding Azure App Registration Demonstration: 1. Complete all the Azure App Registration : Complete the Azure App Registration process as mentioned in the blog  Setting up OAuth Authentication .  2. Change the Redirect URL in Azure App Registration: Change the Redirect URL in Azure App Registration > Authentication to https://businesscentral.dynamics.com/OAuthLanding.htm 3. Azure Active Directory Application: In Business Cen

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