Small and medium business | Business Central, N...

Extension Publish Error failed with code UnprocessableEntity

(3) Share

Report

Posted on by Nick Webb

849

Everything was working fine on Wednesday but when I try to publish and debug an extension from Visual Studio Code to the Cloud Sandbox this morning, it's failing with:-

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've tried various extensions and they're all failing, but were working on Wednesday. No changes in between?

I have the same question (1)

All responses (12)

Answers (0)

Suggested answer

Community Member on at

Like (1)

Report

RE: Extension Publish Error failed with code UnprocessableEntity

Hi,

It look like the permission issue. Please check and verify the License details.

Was this reply helpful? Yes No
Nick Webb 849 on at

Like (1)

Report

RE: Extension Publish Error failed with code UnprocessableEntity

Thanks for your response. I don't believe anything has changed since Wednesday regarding Licensing. It's the Sandbox.

Here's some more information:-

I am able to manually upload, publish and install extensions in the 'Setup & Extensions' page in BC. It's only when attempting a test run from Visual Studio Code that I'm getting the error.

Regarding permissions, it also reports:-

To view details about your permissions, see the Effective Permissions page. To report a problem, refer to the following server session ID: '72171'.

What am I looking for in Effective Permissions?

Was this reply helpful? Yes No
Lars Lohndorf-Larsen on at

Like (1)

Report

RE: Extension Publish Error failed with code UnprocessableEntity

Hello,

For SaaS, also check that you are in a "D365 EXTENSION MGT" group as per:

Installing Extensions to Customize Business Central - Business Central | Microsoft Docs

However how this has suddenly changed, I can't say.

Was this reply helpful? Yes No
Nick Webb 849 on at

Like (1)

Report

RE: Extension Publish Error failed with code UnprocessableEntity

Surely, the fact that I can manually manage extensions in BC means I must have the required permissions? Here's what I've got set in my User Card:-

D365 BUS PREMIUM D365 Premium Business Access CRONUS UK Ltd.
D365 EXTENSION MGT Dynamics 365 Extension management
D365 INTERNAL ADMIN Export data CRONUS UK Ltd.
D365 TROUBLESHOOT D365 Troubleshoot CRONUS UK Ltd.
EXCEL EXPORT ACTION D365 Excel Export Action CRONUS UK Ltd.

By the way, has anyone noticed the word obsolete next to D365 EXTENSION MGT / (Obsolete) D365 Extension Mgt. in Effective Permissions.

Was this reply helpful? Yes No
Brian Wick on at

Like (1)

Report

RE: Extension Publish Error failed with code UnprocessableEntity

Hi Nick,

I can comment on your last question;

docs.microsoft.com/.../deprecated-features-w1

Was this reply helpful? Yes No
Suggested answer

Steven Renders 5,672 Moderator on at

Like (1)

Report

RE: Extension Publish Error failed with code UnprocessableEntity

This seems to be a known 'bug': https://www.yammer.com/dynamicsnavdev/threads/1205490514788352

Is it possible that your sandbox trial has expired? Can you try it on another Saas sandbox?

Was this reply helpful? Yes No
Nick Webb 849 on at

Like (1)

Report

RE: Extension Publish Error failed with code UnprocessableEntity

I'm trying an alternative, newly created, BC Test setup now but I'm not sure if it's a Sandbox? When I hit the Question Mark button and 'Help & Support', it reports:-

Version: GB Business Central 18.1 (Platform 18.0.24800.25676 + Application 18.1.24822.24906)

Azure AD tenant: 16c0745f-3d46-449f-ad50-311a2f4c04e0, Environment: Production (Production)

Session ID (client): 5f066e95-578a-4189-b8fa-17b5fb1b71c1

Is this a Sandbox? If No, what should my launch.json look like?

Was this reply helpful? Yes No
Suggested answer

Steven Renders 5,672 Moderator on at

Like (1)

Report

RE: Extension Publish Error failed with code UnprocessableEntity

No it's not a sandbox, it says: Environment: Production (Production) so it's a production environment. VSCode can not publish to a production environment, only to a sandbox. So create a sandbox and publish to that...

Getting Started with AL - Business Central | Microsoft Docs

JSON Files - Business Central | Microsoft Docs

Example:

Was this reply helpful? Yes No
Nick Webb 849 on at

Like (1)

Report

RE: Extension Publish Error failed with code UnprocessableEntity

Just to add my experience of this error: Originally I got the error because I was pointing at a production environment not a sandbox, so that was quickly fixed. But then after 30 days of using the sandbox, the error started happening again. I later found out that the trial period for the sandbox needed extending and by going to page 1828 in BC, I was able to extend for another 30 days. All this makes the error message: 'failed with code UnprocessableEntity. Reason: You do not have the following permissions on TableData Published Application: IndirectInsert', horribly misleading. Wouldn't something like 'Your Trial Period has expired' be more helpful?

1 people found this reply helpful.

Was this reply helpful? Yes No
Indira88 972 on at

Like (1)

Report

RE: Extension Publish Error failed with code UnprocessableEntity

This has started happening for my sandbox any idea why this happens?

Was this reply helpful? Yes No