Hello Friends,
This was very common issue with Business Central
Microsoft automatic uninstall (unpublished) the extension once the Sandbox environment automatic upgrade by Microsoft.
One of our client raise the ticket to Microsoft and we got following response.
Findings:
Sandbox extensions get deleted after upgrade.
Scheduling upgrade.
My recommendations:
The sandbox environment is not similar to production. If the extensions are not proper the productions upgrade does not proceed pointing to the issue of the extensions etc.
As sandbox is usually for preview and check/do the development, Microsoft do upgrade the sandbox as and when we have the upgrades, so to avoid the extension issue Microsoft does remove the PTEs and keep only the MS extensions in the sandbox. I am very sorry to say,this is by design from the earliest version on SaaS environment and it is going to be like this for a while.
Explained here as well.
For more details, please check the below link.
Outcomes:
There are 2 ways to publish extension in Sandbox
once you upload the PTE extension and than after to publish same extension with same id and app name from vs code than you will get following error
Multiple published extensions match the specified parameter values. You must specify more information to indicate which extension to use
Potential solution: unpublished the PTE in sandbox and changed the id, name, version and publisher of DEV extension
That's it about this topic,
I hope you get some useful information here.
Thank you for reading.
Keep Sharing.....Keep Growing.....
This was very common issue with Business Central
Microsoft automatic uninstall (unpublished) the extension once the Sandbox environment automatic upgrade by Microsoft.
One of our client raise the ticket to Microsoft and we got following response.
Findings:
Sandbox extensions get deleted after upgrade.
Scheduling upgrade.
My recommendations:
The sandbox environment is not similar to production. If the extensions are not proper the productions upgrade does not proceed pointing to the issue of the extensions etc.
As sandbox is usually for preview and check/do the development, Microsoft do upgrade the sandbox as and when we have the upgrades, so to avoid the extension issue Microsoft does remove the PTEs and keep only the MS extensions in the sandbox. I am very sorry to say,this is by design from the earliest version on SaaS environment and it is going to be like this for a while.
Explained here as well.
Regarding the
scheduling.
Scheduling
environment updates is not available
for monthly service updates. For these, the update is applied to tenant
environments as it becomes available. No notifications are sent to tenant
administrators prior to the update. Notifications are sent only after the
update is applied.
For more details, please check the below link.
Outcomes:
There are 2 ways to publish extension in Sandbox
- PTE (Per Tenant Extension) Upload manual from Extension Management page
- Dev Extension - Publish from direct VS Code
Dev Extension are unpublished automatic during upgrade while PTE extension still available in sandbox after upgrade.
Tips: If you need debug facility than never upload extension in sandbox from Extension Management page, you should always deploy it from VS Code.
once you upload the PTE extension and than after to publish same extension with same id and app name from vs code than you will get following error
Multiple published extensions match the specified parameter values. You must specify more information to indicate which extension to use
Potential solution: unpublished the PTE in sandbox and changed the id, name, version and publisher of DEV extension
That's it about this topic,
I hope you get some useful information here.
Thank you for reading.
Keep Sharing.....Keep Growing.....
