Skip to main content

Changes in Permission Sets in Business Central


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.


  • Understanding of Permission Set Objects
  • Understanding of how Permission Sets work.

Books & References: 


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"


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


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: 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 update your Business Central to Latest CU

Introduction:  There are times when Microsoft releases the latest major version upgrade for Business Central Upgrade and you face many issues with it. As soon as the bugs are reported to Microsoft, they start to fix them and ask you to upgrade to a certain Cumulative Update. In this blog, I will be sharing my experience with Business Central v21 CU0 upgrade to Business Central v21 CU2. Pre-requisites:  Business Central DVD for Latest CU Basic Understanding of Business Central CU Updates Books & References:  List of Update Packages How to Update CU version Demonstration:  1. Check the current state of BC: As part of knowing the current state of your Business Central environment, I'm assuming that your Business Central Environment will have some data in the standard Base App also there will be customization with extended tables and newly created tables. Customization - TableExtension on Customer Table  Customization - Custom Table created Make a note of the data that is present i