RAD publishing gives permission errors
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 881
- Forks
- 285
- Avg merge
- 3d 36m
- Merged PRs (30d)
- 1
Description
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
- Open repro workspace: rad-bug-repro.zip
- 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
Issues that are similar
#7267
#7169
#7175
Internal work item: AB#548305
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached rad-bug-repro.zip workspace and CustomerListExt2.PageExt.al, following the listed Business Central 24.3 RAD publishing steps. Compare a normal publish with RAD publishing after uncommenting line 32, and inspect the debugger and web-client permission errors. Done means RAD publishing no longer produces the permission errors or causes the PartName factbox to disappear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100