You do not have the following permissions on TableData Published Application: IndirectInsert.

Gurn69

Good Morning All,

Hope everyone is well and safe.

I have come across an issue that has caused me confusion. I have created an extension that previously was publishing ok to the sandbox instance however when i try publishing the same extension with some changes I am getting the following error

The request for path /v2.0/sandbox/dev/apps?SchemaUpdateMode=synchronize&DependencyPublishingOption=default failed with code UnprocessableEntity. Reason: You do not have the following permissions on TableData Published Application: IndirectInsert.

I have tried publishing this extension to another instance and that is working fine. I also created a new project with the Hello World and tried publishing this to the company sandbox but got the same error message. Only thing I can think of is that it could be a licensing issue now as like I states it was working previously. Could this be the reason or am I going down the wrong path?

Any help or guidance would be appreciated?

Regards
Gurn

Fommo

I have the exact same issue. I could publish to BC Sandbox without problem last week and now suddently I get this error.
Looking at the effective permissions it seems to be a conflict:

The conflict claims that my SUPER role conflicts with the Entitlement. The SUPER role tries to set the Insert and Modification rights to "Yes", but the Entitlement only allows "Indirect".

But I have no clue how to solve this.

A_Prach

I have the same issue after the update in BC 18.1. My user is SUPER so it's not a permission issue but what is it ?

Aluan

Hello,
do you have the SUPER permission for all Companies?
See here:
https://github.com/microsoft/AL/issues/5975#issuecomment-647451581
Edit: Another "solution":
https://community.dynamics.com/nav/b/olisterrs-nav-bc-blog/posts/permission-issues-on-posting-after-deploying-extension-in-business-central-production-tenant

chbraeunlich

Hello,
very interesting issue for sure and I try to fix the same issue for weeks now.

Any updates on this?