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
#Dyn365BC2020.09.15Dynamics 365 Business Central: Extension Management page and the “Delete Extension Data” option
#Dyn365BC2020.09.09Creating lightweight Teams bots with outgoing webhooks and Azure Functions
#Dyn365BC2020.09.01Dynamics 365 Business Central: adding partner’s telemetry on your apps
#Dyn365BC2020.08.28Dynamics 365 Business Central Sandbox Docker containers and multitenancy
