I’ve written a lot in the past about handling breaking schema changes on extensions and the best practice to use the ObsoleteState object property to signal to your developers or third-party ISV users of your extensions that you’re planning to remove something in your codebase. You can find articles here and here.
Today I want to write a quick post for talking about events and about a worst…
Continue Reading demiliani’s Article on their blog
Dynamics 365 Business Central: obsoleting events
I’ve written a lot in the past about handling breaking schema changes on extensions and the best practice to use the ObsoleteState object property to signal to your developers or third-party ISV users of your extensions that you’re planning to remove something in your codebase. You can find articles here and here.
Blog Syndicated with demiliani’s Permission
More About This Author
Array
Dyn365BC2022.06.29Testing multiple Azure Functions apps running together with Microsoft Tye
Dyn365BC2022.06.23Dynamics 365 Business Central: set up alerts on job queue failures
Dyn365BC2022.06.14Do you have Azure Functions in production? Update your Azure Functions apps to use runtime version 4.x
Dyn365BC2022.06.13Dynamics 365 Business Central: introducing the Dynamics 365 Translation Service Visual Studio Code extension (preview)
