Dynamics Community Forum Thread Details

Business Central SaaS Publish Fails with "Specified part does not exist in the package"

Environment:

Business Central SaaS
Publishing from VS Code using AL extension
Target environment: UAT Sandbox
SchemaUpdateMode tested with both Synchronize and ForceSync

Issue:

When publishing my extension from VS Code, the publish fails with:

The request for path /v2.0/<Environment>/dev/apps?tenant=<tenant>&SchemaUpdateMode=forcesync&DependencyPublishingOption=default failed with code UnprocessableEntity.

Reason: Publishing failed due to 'Specified part does not exist in the package.' The original extensions have been restored.

Build completes successfully, but publish fails during deployment.

What I have already tried:

Deleted:
- .alpackages
Downloaded symbols again.
Cleared credentials/cache.
Rebuilt the project successfully.
Removed documents/files that were recently generated by an AI documentation tool and stored in the project folder.
Reverted to a previously working version of the source code and rebuilt.
Tried publishing using both:
- Synchronize
- ForceSync
Generated a fresh .app package.
Verified that the extension compiles without any AL errors.
Tested publishing a completely new/blank AL extension to the same environment.

Important Finding:

A brand-new AL extension publishes successfully to the same UAT environment.

This suggests:

Environment is healthy
Authentication is working
VS Code publishing works
Issue appears to be specific to this extension/package

Questions:

What exactly does "Specified part does not exist in the package" refer to in Business Central extension publishing?
Are there known cases where:
- Report layouts (Word/Excel/RDLC)
- Translation files (.xlf)
- Control AddIns
- Embedded resources
- Package manifest issues
  can cause this error even when the extension builds successfully?
Is there a way to identify which specific package part/resource is missing?
Are there server-side logs or telemetry that can provide more details using:
- Request ID:
- Session ID: