Home of the Dynamics 365 Business Central AL Language extension for Visual Studio Code. Used to track issues regarding the latest version of the AL compiler and developer tools available in the Visual Studio Code Marketplace or as part of the AL Developer Preview builds for Dynamics 365 Business Central.
1. Describe the bug
If we use RAD publishing our app becomes unusable because we are getting a lot of permissions errors and factboxes disappear (probably because of missing permissions)
Add launch settings for a version DE 24.3 sandbox to workspace file
Download symbols
Publish full dependency tree
Open the "Customer List" 5 messages are shown and factbox "PartName" appears at the end of the factboxes
Uncomment line 32 in CustomerListExt2.PageExt.al (or add some changes to this file)
RAD publish with debugging
Open the "Customer List" again.
Debugger breaks and permission errors are shown in the web client
3. Expected behavior
RAD publishing should not give permission errors
4. Actual behavior
RAD publishing is giving permission errors
It looks like the permission is only given, if the object is included as a RAD change.
If you e.g. change something in the codeunit and RAD publish, you are not going to get the permission error for the codeunit.
AND: It also works if you give the objects the InherentEntitlements = X; property.
More information:
I have SUPER permissions
Everything works, if I am not RAD publishing (e.g. normal publish or full dependency tree)
I am using object ids outside of the 50000..99999 range (because I am trying to RAD publish our product and not a customer PTE)
5. Versions:
AL Language: Version: 14.0.1070882
Visual Studio Code: Version: 1.91.1 (user setup)
Business Central: DE BC24.3
List of Visual Studio Code extensions that you have installed: Does not work even with only AL vsix enabled
1. Describe the bug If we use RAD publishing our app becomes unusable because we are getting a lot of permissions errors and factboxes disappear (probably because of missing permissions)
2. To Reproduce
CustomerListExt2.PageExt.al
(or add some changes to this file)3. Expected behavior RAD publishing should not give permission errors
4. Actual behavior RAD publishing is giving permission errors
It looks like the permission is only given, if the object is included as a RAD change. If you e.g. change something in the codeunit and RAD publish, you are not going to get the permission error for the codeunit. AND: It also works if you give the objects the
InherentEntitlements = X;
property.More information:
5. Versions:
Issues that are similar
7267
7169
7175
Internal work item: AB#548305