More than an year ago I’ve written this post explaining how to handle breaking schema changes on a production Dynamics 365 Business Central SaaS tenant. I think that every Dynamics 365 Business Central developer now knows that in a production environment you cannot remove objects or fields (breaking schema in the database) but all schema changes must always be additive.
Despite this, I see…
Continue Reading demiliani’s Article on their blog
Dynamics 365 Business Central: again about obsoleting fields
More than an year ago I’ve written this post explaining how to handle breaking schema changes on a production Dynamics 365 Business Central SaaS tenant. I think that every Dynamics 365 Business Central developer now knows that in a production environment you cannot remove objects or fields (breaking schema in the database) but all schema…
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)
