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
Business Central24 April 2024Dynamics 365 Business Central: Edit in Excel and Long Running SQL queries
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.
