Greetings,
I am going to preface this post with the statement that we do very little with on-premise Business Central environments,
We have developed an extension for our on-premise client that uses a new codeunit with an object ID of 50001. In the extension, we define a new permission set that includes the Execute permission for this new codeunit, and the main user that will be accessing/testing the extension has been assigned to the permission set (and she is also SUPER). The issue is that calls to the procedures in the codeunit fail with "Sorry, the current permissions prevented the action: Execute." When I look at the permission set, the Execute action is defined, but the effective permissions for that show nothing at all in the Execute column for that codeunit. Copying the permission set and creating a user-defined set with the explicit Execute permission presents the same behavior.
What are we doing wrong? How do we fix this?
62
Share
Report
All responses (
Answers (
