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

Post a Comment

Let me know your comments below. I'll try my best to answer your comment

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

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe