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 information below explains the steps to follow while rolling standard costs in Dynamics NAV. The process is relatively simple, but the goal of this document is to explain the importance of each step: and what is accomplished in those steps. So while this may appear to be a long blog, stick with is as it provides a thorough explanation and rationale of each step.
Recently, I came across a customer, where a partner had implemented some Stored Procedures on a Microsoft Dynamics NAV 2017 database.
Now, for any change on SQL level that comes to my ears, my first reaction is always “Nooooooooo“. Or as a pictures tells more than a thousand words: