Skip to main content

Notifications

Business Central forum
Answered

Upload extension to next minor version failed - why?

Posted on by 4
Hi folks, 
 
I am encountering a very weird issue while uploading and scheduling a customized extension (new version: 1.0.0.38) in our production environment for the next minor update: the upload failed and the error message is /Deploy Operation rejected. Error: The application extension with app id 'xxx' cannot be staged for future deployment because there is no existing deployed version to upgrade from./ 
 
This is weird because a previous version (which is 1.0,0.37) of the extension has been successfully installed in our business central tenant. When we set the version number of the .app package back to 1.0.0.37 and tried to schedule this version to the next minor update, we have got another error message stating: An extension with app Id 'xxx' and version at least '1.0.0.37' is already installed on this environment
 
The newer version of the extension 1.0.0.38 contains the newest symbols of the next minor version (which we have downloaded from our test environment that has been updated recently to the newest minor version 22.3).
 
The production environment is currently at 22.2 and should be upgraded to 22.3 soon. 
 
I have also inquired our business central partners but unfortunately, they couldn't help us with this issue. 
 
Could someone please give me a hint why the scheduling fails? (without deleting the extension manually shortly before the next scheduled update window).
 
Thanks!! 
Categories:
  • grantb Profile Picture
    grantb 25 on at
    Upload extension to next minor version failed - why?
    Hi Deman:
     
    when you say you replaced your current app with a higher version, what do you mean?
     
    I have a version 22.0.3.0 installed. I'm trying to install 22.3.3.3. Going from BC 22.2 to 22.3. I get the exact same thing. the app id they say isn't deployed is in fact deployed.
     
    Thx.
  • Upload extension to next minor version failed - why?
    Hi ZHU,  
     
    thanks a lot for your quick response. 
     
    I have solved this issue by replacing our current app with a higher version. Then the scheduling works with the app that contains changes for the next minor release. 
    So the installation of our app with version 1.0.0.37 seems to be somehow faulty, just like you have suggested. 
     
    And I appreciated your advice by testing it out with a sandbox. :)   
     
    Btw, I have been reading your blog posts and they have helped me a lot to get first technical insights regarding business central. 
    Thanks a lot for your contribution and willingness to share your knowledge! 
     
    Best regards, 
    Deman
  • Verified answer
    YUN ZHU Profile Picture
    YUN ZHU 71,307 Super User 2024 Season 2 on at
    Upload extension to next minor version failed - why?
    This is kind of weird, did the app id change?
    You can copy the production environment and test it in Sandbox to see if there is any problem with the current version installation.
    And if this issue has not been resolved, it is recommended to submit a Service Request to Microsoft for their assistance in investigating.
     
    Hope this helps.
    Thanks.
    ZHU

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 290,818 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 229,147 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans