However, if your app contains thousands of AL files, this can take longer. Submissions are generally processed within a few minutes and we expect all submissions to be processed under 3 hours. Depending on the size of your app, the validation time can vary. If you already have a version of these extensions published to AppSource, then it will also run the breaking change validation using the apps currently in AppSource as baseline.
How long does the 'Automated application validation' take?ĭuring 'Automated application validation', the apps in your submission are validated for each of the country/regions and each of the releases of Business Central targeted. In order to keep the listing(s) in sync with the version of the app(s) uploaded to Business Central, you should submit a submission for their related offer(s). If one or more libraries in your submission have their own offer, their listing(s) in the AppSource marketplace won't be updated automatically. If B is updated to depend on C and D, then all apps in the submission will now be validated by the service. C and D will be ignored because they are not required by the main app A. If you create a new submission with A as the main app and include B, C, and D as libraries, then only A and B will be validated.
If you have included libraries which are not required by the main app, they will be ignored during the validation and will not be uploaded to the service.įor example, let's consider an app A which has an offer in the AppSource marketplace and A depends on a library named B which doesn't have any dependencies. The main app and the libraries required by the main app are validated and uploaded to Business Central. Which apps are validated in my submission? You should then not submit your app to the AppSource marketplace if you are still developing it and expect to change it in the near future.
This applies also if your extension isn't used by customers yet. As a consequence, you won't be allowed to perform breaking changes without obsoleting the AL objects first and you won't be allowed to perform schema breaking changes breaking changes on tables or table extensions. You can know which versions of your extensions were used as baseline during the breaking change validation by enabling Azure Application Insights in your extension and running this Troubleshooting Guide (TSG).Īs soon as your app has been uploaded to the AppSource marketplace, it will be used as a baseline during the technical validation of your next submissions. The service will verify that your extensions do not introduce breaking changes by comparing them to the latest version available in AppSource for each country validated. Against which baselines are my apps validated? If you are using Azure Application Insights, you can check whether the country/region was validated using this Troubleshooting Guide (TSG). When the localization becomes available, if you are experiencing issues installing your apps, you should increase the version in the app.json and submit the packages again in Partner Center. Generally, it is possible to upload apps for 'Planned' localizations a few weeks before they are officially released. If you are targeting a country/region marked as 'Planned' in Country/regional availability, depending on when your submission is processed, your apps might not be uploaded to Business Central if the localization isn't yet ready in Business Central. Note that when adding new localizations in Business Central, these countries/regions can be added to Partner Center before they are actually ready in Business Central. You can see which countries/regions you have selected in Partner Center under Availability > Edit Markets. The extensions in your submission are validated for all the countries/regions targeted by the submission which are available in Business Central. Against which countries/regions are my apps validated?
The goal is to ensure that your customers won't be blocked during the upgrade of their environment. The apps in your submission must then be compatible with the upcoming release. 30 days before the release of a new Business Central major version, all submissions are validated against the upcoming release.