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
Dyn365BC2023.01.26Dynamics 365 Business Central 2023 Wave 1 release plans pillars- Dyn365BC2023.01.25Dynamics 365 Business Central: retrieving Azure AD User informations via AL
- Dyn365BC2023.01.18Telemetry with Azure Application Insights: prevent anomalies on data ingestion
- Dyn365BC2023.01.16Dataverse Virtual Table Creation Wizard (preview)
