In Business Central 2022 wave 2 (BC21), Microsoft has finally added a new command to generate or update AL permission set. From now on, whether it is PTE or AppSource Extension, permissions should be managed in the permission set object.
Today I would like to talk about Permission Exclusion in Business Central.
This was originally a new feature of Business Central 2022 wave 1 (BC20).
More details from Business Central Launch Event 2022 Release wave 1 (BC20):
There are two things that developers in AL do not like to do. Reports – I know very few people who like it, and Permissions. Although in my case I should say I do not like only one thing since permissions I just HATE.
In the next two weeks, we plan to release a new extension on AppSource (stay tuned) and we need to do permissions – as always. I sat with one of our developers and we decided “let’s do it in a new way”.
I am sure you would have created the functionality mentioned in my previous blogs. If you still have not, refer to Customer Requirement for AL Development where I have explained in details about Developing Extension in AL.
In this blog we will discuss about generating persmession set , which is simple and can be done in 2 steps by automated process for any Extension.
When developing in AL creating permission sets isn’t the must fun thing to do…. I thought it must be possible to find a better tool than editing the xml file manually and found some inspiration here. Based on that I created this excel sheet that you can use to create a permission set xml file.