Sorry, the current permissions prevented the action. (Codeunit, D365 BC API)

(1) Share

Report

Posted on by j_ha_e

Hi,

I tried to publish a webservice. The object is a simple code unit with following content:

codeunit 80004 TutorialAPI

{
procedure Hello(): Text
begin
exit('Hello World');
end;
}

The Azure Active Directory App has got following user groups and permissions:

A POST to https:/api.businesscentral.dynamics.com/v2.0/{{Tenant-ID}}/{{Env_Name}}/ODataV4/TutorialAPI_Hello without any json payload will bring up following error with status code 400 bad request and message:

{
    /error/: {
        /code/: /Internal_ServerError/,
        /message/: /Sorry, the current permissions prevented the action. (CodeUnit TutorialAPI Execute: )  CorrelationId:  d335ed99-1ac4-4029-9815-f9048e8d05d7./
    }
}

I can't figure out what the problem might be. Hopefully someone has an idea.

Greatings

Jannis

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

YUN ZHU 98,819 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi, it looks like you didn't generate the permissions file for your extension. More details: https://yzhums.com/29221/

For exmaple,

Also, this is required in a production environment.

Hope this helps.

Thanks.

ZHU

Was this reply helpful? Yes No
j_ha_e 9 on at

Like (0)

Report
Copy link

Link copied!

Hi Yun Zhu,

thanks for your quick response. I tried it as the article suggest it with the following permission set:

permissionset 80000 GeneratedPermission

{

Assignable = true;

Permissions =

codeunit TutorialAPI=X;

}

And assigned it to the Azure Application:

Unfortunately the result ist the same:

{

    "error": {

        "code": "Internal_ServerError",

        "message": "Sorry, the current permissions prevented the action. (CodeUnit TutorialAPI Execute: )  CorrelationId:  2c526749-1586-490a-8331-cfd04f9abae7."

    }

}

Is there a step I missed out?

Was this reply helpful? Yes No
j_ha_e 9 on at

Like (0)

Report
Copy link

Link copied!

Hi Yun Zhu,
now it works. I re-added the permission in the permission sets of the app user without a specific company.

Thanks for your help.

Greetings

Jannis

Was this reply helpful? Yes No