Deploying a new version of the dependent extension

After performing the data upgrade of the main extension to a new version, we saw that the dependent extension has been broken. It is crucial at this stage to let the user read or update the new NewCatalogueNo. field from the client.

First things first. We must bump the app.json version of the dependent extension to 2.0.0.0, and also update the dependency to the appropriate version of the main extension. See the following updated snippet:

"version": "2.0.0.0","dependencies": [    {        "appId": "15ecd2e5-b7a8-4612-ae6f-d722af29c0c0",        "name": "MainExtension",        "publisher": "DTacconi Inc.",        "version": "2.0.0.0"    }],

When the app.json file is updated, we must download the new symbols from our multitenant ...

Get Mastering Microsoft Dynamics 365 Business Central now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.