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.
With the refactoring done in Dynamics 365 Business Central for better supporting the SaaS environment, is not quite easy to check if a user has a specific permission on a specific object.
Permission Range table is now a system table that cannot be used on a SaaS environment, License Permission table does not give you specific user permissions and using the ReadPermission and WritePermission methods (that can determine if a user has read and write permission on the object) is only available for table objects and often this is not enough if you have complex security checks to implement (for example if you want to test if your user has execute permissions on a specific codeunit).
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.
Microsoft partners who build solutions based on Business Central need a way to expose access to their custom objects through so-called System permission sets. These permission sets are read-only, but users can copy them to create User-Defined permission sets with different permissions. All permission sets released by Microsoft are also of type System.
How Do I: Automatic Recording Permissions in Microsoft Dynamics NAV 2016
One of the new super useful features in Microsoft Dynamics NAV 2016 is the capability to record table data permissions by simply going through the process in the application.
For those of you that have been implementing NAV/Navision when the classic client was around are probably familiar with this process since the classic client came with a client monitor which results you could turn into permissions quite easily. I did this all the time in the ‘old days’, but since the replacement of the classic client I have not found a good way of recording permissions until now. So, for me this feature brings me ‘back in business’ when it comes to setting up permissions in a proper way
With a new project implementation, after mapping customer gaps in the standard database, importing opening balances, and importing master data, we all have had issues in previous versions of Microsoft Dynamics NAV assigning permissions to users. For every user, we need to map the Permission Set they require to access the system.