Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
When an app is submitted for AppSource, a per-tenant extension is submitted, or when a tenant is about to be upgraded, the Application Validation Service is run. This article gives an overview of the diagnostics that running the AVS tool gives, sorted by ID and severity. For more information about a specific diagnostic, choose the ID.
| ID | Message | Default Severity |
|---|---|---|
| AVS0001 | The 'app.json' could not be found in the specified package. | Error |
| AVS0002 | The runtime version '{0}' of the extension is too recent for the release of Business Central being validated. The latest supported runtime version is '{1}'. | Error |
| AVS0003 | The file '{0}' could not be added to the file system because a file with the same name already exists. | Error |
| AVS0004 | The specified ruleset could not be loaded. Details: {0} | Error |
| AVS0005 | A package with publisher '{0}', name '{1}', and a version compatible with '{2}' could not be found. | Error |
| AVS0006 | The runtime version '{0}' is not supported for the release '{1}' because its latest supported runtime version is '{2}'. | Error |
| AVS0007 | The release version '{0}' is not supported. | Error |
| AVS0101 | A package with publisher '{0}', name '{1}', and a version compatible with '{2}' could not be found. | Error |
| AVS0102 | A package with publisher '{0}', name '{1}', and a version compatible with '{2}' could not be loaded. | Error |
| AVS0103 | The extension with ID '{0}' appears multiple times in the submission, while all extensions submitted are expected to have a unique ID. | Error |
| AVS0104 | The extension '{0}' by '{1}' (version '{2}') is a runtime package, which is not allowed in Business Central online. | Error |
| AVS0105 | The submission must target at least one existing release of Business Central. Verify the dependencies specified in the app.json of all the apps submitted. For more information about the target release computation, see the examples in the Technical Validation Checklist at https://aka.ms/CheckBeforeYouSubmit.|Error| | |
| AVS0106 | The submission must target at least one existing country/region of Business Central. Verify that at least one country/region is marked as 'Available' at aka.ms/bccountries. For more information, see the Technical Validation FAQ, at https://go.microsoft.com/fwlink/?linkid=2182737.|Error| | |
| AVS0107 | The extension '{0}' by '{1}' (version '{2}') has already been uploaded to Business Central for the country/region '{3}' with different content. Remove this extension from your submission, use the same .app file as the one that has already been uploaded to Business Central, or increase the version in the app.json. For more information, see the Technical Validation FAQ, at https://go.microsoft.com/fwlink/?linkid=2182737.|Error| | |
| AVS0108 | The following extension(s) could not be found. Upload the missing extensions and try again. {0}. | Error |
| AVS0109 | The per-tenant extension (or one of its dependencies) cannot be deployed as it has missing dependencies or the dependencies are conflicting with currently installed apps. Check if these dependencies are installed. | Error |
| AVS0110 | A {0} with ID {1} is found in both {2} and {3}. Object IDs must be unique per environment. Resolve the conflict in your extension by using a different ID and upload the extension again. | Warning |
| AVS0111 | A {0} with name '{1}' is found in both {2} and {3}. Object names must be unique per environment. Resolve the conflict in your extension by using a different name and upload the extension again. | Warning |
| AVS0112 | A {0} with ID {1} in '{2}' is found in both {3} and {4}. {0} IDs must be unique within the base objects and their extension objects. Resolve the conflict in your extension by using a different ID and upload the extension again. | Warning |
| AVS0113 | A {0} with name '{1}' in '{2}' is found in both {3} and {4}. {0} names must be unique within the base objects and their extension objects. Resolve the conflict in your extension by using a different name and upload the extension again. | Warning |