I’ve received a request from a partner asking why adding a return value to a procedure in a Dynamics 365 Business Central extension that previously had no return value is considered a breaking change during AppSource validation.
The explicit question was: “if previously I had a dependent extension that uses the first version of this procedure (the version without return value) and now I…
Continue Reading demiliani’s Article on their blog
Dynamics 365 Business Central: breaking change when adding a return value to a procedure
I’ve received a request from a partner asking why adding a return value to a procedure in a Dynamics 365 Business Central extension that previously had no return value is considered a breaking change during AppSource validation. The explicit question was: “if previously I had a dependent extension that uses the first version of this…
Blog Syndicated with demiliani’s Permission
More About This Author
Array
Business Central15 April 2024Dynamics 365 Business Central 2024 Wave 2 release plans: “as is” and “to be”
Business Central10 April 2024Dynamics 365 Business Central and Shopify connection: access key rotation.
Business Central10 April 2024Azure Functions: .NET 7 support is ending and you should upgrade to .NET 8.
Business Central4 April 2024Dynamics 365 Business Central 2024 Wave 1 release: important server changes to remember.
