5
No matter how much I search, the update schedule is postponed, and there is nothing to turn off the automatic update function at all. Since we develop Extensions, if Business Central is updated automatically, we don't want to have to do additional development to match that version.
Hi, just to add some info.
If you use the SaaS version, Microsoft also has the following strategy, you must adapt your app to the current version as soon as possible.
When apps or PTEs cannot be updated by Microsoft
This section describes the processes that are initiated during and after upgrade attempts of code provided by publishers of apps or PTEs. For information about handling a PTE that has conflicts with another extension, see Upgrading Per-Tenant Extensions that Conflicts with Other Extensions.
T+1 – T+30: Microsoft alerts administrators, resellers, and ISVs
Shortly after a service update of Business Central online (Day T), Microsoft will initiate daily updates attempts on all tenants. In these update attempts, the publisher's provided upgrade code is triggered and run. These attempts run repeatedly in a time frame of approximately one month until the upgrade is successful. For more information, see Major Updates of Business Central Online.
With every unsuccessful upgrade attempt, stakeholders will receive notifications. Customers and their reselling partners can follow these notifications in the Business Central administration center.
ISVs who provide third-party AppSource apps might not be listed in the customer's admin center. The reseller will in most cases have worked with the ISV to test compatibility, but after two weeks (Day T+15) of failed upgrade attempts, the Microsoft AppSource team will also send the app provider a warning message that action within the next few days is required. Incompatible extensions can be uninstalled within 14 days if they prevent deployment of security updates.
This message will explain that if they fail to respond correctly, their app will be removed from AppSource at Day T+30.
T+30 – T+60: Microsoft alerts the customer
After one month of failed upgrade attempts (Day T+30), the customers will be notified again that apps or PTEs are incompatible with the new version of Business Central, and that no further automatic upgrade attempts will be planned until further notice. Although the publisher's code continues to run on an outdated version of Business Central online, the customer must work with their reseller to resolve these issues immediately so that the tenant can be updated. Next to messages in the Business Central administration center, all users in the customer's tenant will also get more active warning about the incompatibilities when they use the product in the browser or their mobile device.
For AppSource apps, if no appropriate action or follow-up was taken by the publisher since the release (T - T+30days), the app will be removed from AppSource. This means no new customer will be able to install the app in a new tenant. The main reason for removing an app from the marketplace is to ensure that no new customers will be affected by incompatibilities with the latest version of the base product, Business Central.
If the publisher wants to have their app available again, they must mitigate all existing incompatibility issues and go through the full validation process again.
If the source of the incompatibility has been resolved by the publisher, they'll have to submit a support request to schedule a new set of upgrade attempts for any tenants that are blocked because of this incompatibility. They'll also have to work with their resellers to inform them about the compatibility resolution.
T+60 – T+150: Microsoft initiates the customer wind-down period
If the incompatibility issues are not resolved at T+60, and the publisher remained unresponsive to the request to resolve the incompatibility, Microsoft may choose to send out a wind-down communication to the customer about removal of the publisher's code.
This communication will share that the code from the publisher will be removed in 90 days from the day of the communication from Microsoft (T+150).
During this wind-down time, the customer and their reselling partner are fully responsible for finding a solution on how to proceed in this situation. If the customer decides to leave Business Central, or decides to use another publisher, they can access their data by exporting the database, use RapidStart Services, or copy data to Excel. For more information, see Exporting Your Business Data to Excel in the business functionality content.
Microsoft may also choose to remove all existing apps by this publisher from AppSource and block the publisher from publishing new apps for Business Central.
If this wind-down period is initiated, and the customer was able to fix the incompatible issues with their reseller and potential publishers, it will be at Microsoft discretion if the publisher's code will be removed from Business Central or not.
Thanks.
ZHU
Hi Kurago - As suggested by Mohana, the main idea behind SaaS is automatic environment upgrades. However I think the problem may be different here - I do not understand why would there be a need to do any kind of additional development every 6 months? I'd suggest turn on the AL Code Cop in your VS extensions and get rid of warnings before they become errors. If you're suggesting you are writing extra lines of code every time an upgrade happens, it strongly points towards the fact that something's very very wrong with those extensions. That's not how AL code works, nor does the concept of extensions work.
I've had extensions deployed in 2019 which have not troubled me till date.
Alternatively, try using On-Prem, your automatic upgrade problem will be solved
Indeed, BC Saas will be auto updated and you can not stop that, and that's a good thing :-)
Developers need to maintain their code and make it compatible with new versions.
If you can't do that, I would not like to be your customer...
Main goal of the SaaS version is to keep the customers on the latest version so we cannot stop automatic updates.
Microsoft will give us time window in which we have to schedule the update. Ex. 60 days for major updates.
#1
André Arnaud de Cal...
291,391
Super User 2024 Season 2
#2
Martin Dráb
230,445
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
