Deploying a new version of the main extension

Again, in order to make it very simple, we will create a second version of the main extension where one field, Catalogue No., will change its data type from integer to text 30. This is a data type conversion that constitutes a breaking change in the data schema. The second version of the extension must then cope with the following:

• Increase (bump) the extension version: Change the app.json file version field as follows:

     "version": "2.0.0.0",

• Table or table extension object changes: We should declare the original Catalogue No. field with the ObsoleteState property set to Removed (for a definition of ObsoleteState and an overview of how it is used, please visit https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-obsoletestate-propert...