Skip to main content

Changes in Permission Sets in Business Central

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: 

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 XML File.
To generate Permission Sets as XML file, you can hit Ctrl + Shift + P > Generate permission set as XML file containing current extension object.


you will see an XML file created in your project.



2. Permission Set as Permision Object:
Recently in last year, Microsoft introduced Permission Set as object. For every PTE it is mandatory to have your own Permission Sets.
To generate Permission Sets as XML file, you can hit Ctrl + Shift + P > Generate permission set as AL Object containing current extension object > Provide your permission set name

This will create AL file in your project.

In order to use Permission Sets from Extension, you will need to enable the highlighted property UsePermissionSetsFronExtensions set to TRUE.

Also, from this point onwards, Microsoft started creating Base App Permissions Sets in the Permission App as extension.
Also, for specific localization, there should be a localization specific Permission Sets.

3. To Upgrade Permissions Sets from XML to AL objects:
As per of Upgrade from older versions of NAV/ BC to latest BC, you will need convert your XML permission sets to AL objects.
You can generate AL Objects using Convert-PermissionSets powershell module in Upgrade Permission Sets
You can run the Powershell Scripts as follows -
Import-Module "Your Path\Convert-PermissionSets.psm1"

Convert-PermissionSets -DatabaseServer <ServerName> -DatabaseName <DatabaseName> -Destination "TargetPath"

Conclusion:

I hope this blog provides information to help you in your journey to upgrade from NAV to BC.
Cheers!!




Comments

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Setting up OAuth Authentication for Business Central Web Services / APIs

Introduction: After upgrading Business Central to version 17 (Wave2 2020), I found that there was an error telling me that WebService Key is going to be deprecated soon. Web Service Access Key is deprecated. Hence, I decided to explore and probably make it easier through this blog. Pre- requisites : Admin Access to Office 365 Admin Access to Azure Demonstration: 1. App Registration on Azure Portal: To enable OAuth authentication for any apps in Azure Active Directory, you will need to perform App Registration and set up the permissions and security details. i.) Register the App: Search for 'App Registration' on the Azure Portal. Click on New Registration Type in the App Names, Account Types and Redirect URI. Registering Application ii.) Setup API Permissions: Go to API Permissions > Add Permissions > Business Central App > Select Delegated Permissions > Select Other Permissions and Financials > Add Permissions Button. Setup API Permissions iii.) Setup Client Secr

How to Upgrade Data from Microsoft Dynamics NAV to Microsoft Dynamics Business Central On Premise - Part 2

 Introduction: Now that the first step of the problem preprocessing of the NAV Database to make it ready to be migrated to BC is done(refer Part 1 ), we can now proceed further with connecting the database in 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 https://olisterr.blogspot.com/2022/03/how-to-upgrade-data-from-microsoft.html https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/upgrade-permissions Demonstration: 1. Install Business