I have an app deployed on BC version 18. The client received an email saying that the app will be incompatible after the next update due to some removed tables and said to do the following:
Recommended actions:
|
Option 1: If you require using the above extension, you must resolve compatibility issues in the code of your extension. You may need to contact your Partner to perform this action, Microsoft support will not be able to assist.
|
|
A. Review the breaking changes and how to resolve them. Make the minor change to the extension, compile the extension against the major and minor application version the validation was run against, and perform the necessary tests.
|
|
B. Upload the extension using the Extension Management page in Business Central and select the appropriate version for which the updated extension is compatible. The extension will then be updated to this version immediately or during the next minor or major update. For more information, view Deploying a Tenant Customization.
|
It also contains the following info regarding the specific version the app is incompatible with:
Validation results:
|
Environment: [Client Company]
|
Application Version: 19.4.34845.0
|
How do I do part A? Here a part of my app.json in VS Code:
"dependencies": [
{
"appId": "63ca2fa4-4f03-4f2b-a480-172fef340d3f",
"publisher": "Microsoft",
"name": "System Application",
"version": "18.0.0.0"
},
{
"appId": "437dbf0e-84ff-417a-965d-ed2bb9650972",
"publisher": "Microsoft",
"name": "Base Application",
"version": "18.0.0.0"
}
],
"screenshots": [],
"platform": "18.0.0.0",
"application": "18.0.0.0",
"runtime": "7.0",
I assumed that I would be able to change 18 to 19 in my app.json and download the symbols of the next release. However, if I change any 18 to 19 in app.json i get the following Not Found error:
The request for path /v2.0/Sandbox/dev/packages?publisher=Microsoft&appName=Application&versionText=19.0.0.0 failed with code NotFound. Reason: No published package matches the provided arguments.
I tried publishing the app (without any code changes) with Schedule set to next major version so that it might run the validation on BC itself and I could use those to make sure the app will be compatible with the next release but it 'completed' successfully. I'm assuming it will be installed when BC is actually updated and will fail then since I didnt do any code changes: