Hi, Readers.
Dynamics 365 Business Central 2024 wave 2 (BC25) is generally available. More details: General availability: Dynamics 365 Business Central 2024 release wave 2 (BC25).
I will continue to test and share some new features that I hope will be helpful.
In this post, I would like to talk about The command for generating permission sets is now compatible with namespaces in Business Central 2024 release wave 2 (BC25). This is not yet documented in the Business Central 2024 release wave 2 (BC25) release plan. But it is mentioned in AL Language extension changelog Version 14.0
The command for generating permission sets is now compatible with namespaces.
In Business Central 2021 release wave 1 (BC18), Microsoft released new AL objects – Entitlement, PermissionSet, and PermissionSetExtension. For more information, see Entitlements and Permissions Overview, and Entitlement, PermissionSet, and PermissionSetExtension (New AL objects)
And in Business Central 2022 wave 2 (BC21), there was a new command to generate a permission set as an AL object: al.generatePermissionSetForExtensionObjects. More details: Business Central 2022 wave 2 (BC21): New command to generate or update AL permission set
Next, let’s take a look at the namespace in AL.
Namespaces are used to organize code into logical groups and hierarchies, which can prevent naming conflicts that can occur when libraries are combined. Namespaces ensure uniqueness in code names and allow reuse of names in different contexts, and provide structure for the code base, making it easier to navigate and understand. Namespaces are used in many programming languages and they’re available with AL from Business Central 2023 wave 2 (BC23). More details: Business Central 2023 wave 2 (BC23): Segment AL code and reduce naming conflicts with namespaces (Namespaces in AL) and Namespaces in AL.
For example, page 42 “Sales Order”:
Also available in our customization.
So when generating the permission set from the command, can namespaces be added automatically? With this update (BC25), this becomes possible. Let’s see more details.
When invoking the command, the developer can choose to create a new permission file or select an existing file to update.
After entering the Permission Set name, there is now a new step, enter Permission Set namespace.
The namespace will be saved in the generated permissionset object.
Test video:
Small update, but it makes life easier. Give it a try!!!😁
3. Dynamics 365 Business Central: The namespace ‘xxxx’ is unknown in CalcFormula Property
END
Hope this will help.
Thanks for reading.
ZHU
コメント