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

Business Central PTE Deployment from VS Code get stuck in publishing state

(1) Share

Report

Posted on by Hein Kruger

666

We recently upgraded a customer from onPrem BC20 to Cloud BC28.
Their Database is around 600GB and their PTE Extension has over 950 objects.
This includes Extending objects and new objects.

When we try to publish (Without debugging) from VS code we can see that VScode tries to Publish/Attach to Business Central, which is what we always see.

Next while the Extension is being deployed to a Sandbox Environment we can see in the Extension Management that die extension is listed as a Dev app, but its not been installed yet.
This state stays like this for around 15minutes then the extension shows installed on the Sandbox Environment, but the VScode part never reach the success state. It just keeps trying to deploy.

My question is if there is a PTE object limit or Database limit where Business Central Cloud cant compile DEV extensions anymore?
I saw the other option "Debug without publishing". Is microsoft rather opting that we publish as PTEs and then "Debug without publishing"?

Thanks in Advance

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Khushbu Rajvi. 23,005 Super User 2026 Season 1 on at

Like
a
(2)

Report
Copy link

Link copied!

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-object-specifications-limitations#specifications-for-the-database

Please publish the extension normally. Once it is installed in Extension Management, cancel the stuck publish session, restart VS Code, and check the AL Language Output for a timeout or publish error.

Use Debug without publishing only after the app is already installed, because it debugs the last published version and does not deploy new changes.

If the issue continues, test the same app in a clean sandbox and raise a Microsoft support case with the AL Language Output, publish timestamp, and extension version.

Was this reply helpful? Yes No
Suggested answer

Kamal Khakhkhar 3,481 on at

Like
a
(0)

Report
Copy link

Link copied!

Hii There , as per requirement while deploy extension as PTE , Uninatall Extension Published as DEV.
Due to Extension Deployed As Dev While Publishing As PTE it will Give Error. so check accordingly.

For this you can create a module based architecture to keep TableAndTable Extensions in single extension and Other Extensions are based On Modules Like AllCustomizations , FieldAdditions , ExtendedAddon like that.

as Debug Without Publishing is working on last Deployed Version with DEV or PTE . so if you updated after last deployment it will Debug on Last Deployed version , not on current version.

If you found answer mark it verified.

Thank You.

Kamal Khakhkhar.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Business Central PTE Deployment from VS Code get stuck in publishing state

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Launch!

Women in Power Builds Momentum

Congratulations to the May Top 10 Community Leaders

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates

Community site session details

Business Central PTE Deployment from VS Code get stuck in publishing state

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Launch!

Women in Power Builds Momentum

Congratulations to the May Top 10 Community Leaders

Subscribe to this forum!

Select categories

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates