New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run-AlValidation does not fail validation, but validation fails in Partner Center when submitting the app for NextMajor #2697
Comments
Please include full script of the Run-AlValidation command and if possible, full output as well. |
This looks like you are providing a different app as previousapp than the one you currently have in appsource. |
Hi Freddy, We are currently only targeting the Current market. In the Next Major pipeline, we compile the app to ensure it will pass before we submit the app to AppSource, especially when the range of versions being tested against might include a major version. For some reason, it is passing when running Run-AlValidation in the pipeline or locally, but failing when checked against 21.0. |
We are facing the same issues. I will write you an email containing all artifacts to reproduce. |
Thanks @Walwode - found the issue and will fix this in 4.0.5 (which will be released in an hour or so) |
Special thanks to Quentin for pointing me in the right direction |
fixed in 4.0.5 |
Describe the issue
Running Run-AlValidation when comparing between the current app and previous app in the BC21 NextMajor container
passes without any failure, but when submitting the app into AppSource, it fails Validation due to the Promoted property being removed from the action group in a Page object. The command should have caught that and returned a validation error.
Script used to run AL Validation
Output of script
Output of validation error in Partner Center
AS0031 Error
The action with name 'H&istory_Promoted' defined in Page 'XYZ Card' was found in the previous version, but is missing in the current extension. This will break dependent extensions.
Additional context
The text was updated successfully, but these errors were encountered: