Small and medium business | Business Central, N...

App.json settings for compatibility fixing

(2) Share

Report

Posted on by DinB

4,017

I want to download symbols from BC 28.x Preview Sandbox to VS Code to fix compatibility errors. I want to deploy to v27 Production environment before applying the v28 on Production. What should I enter as versions in the App.json. Following is an example. When I deploy to v27 do I have to change the Platform back to 27.0.0.0? Please advise how I should enter the version numbers development and deployments. Thanks!

{
  "id": "xxxxxx",
  "name": "Extension Name",
  "publisher": "Publisher",
  "version": "28.0.0.1",
  "logo": "",
  "dependencies": [
    {
      "id": "xxxxxx",
      "publisher": "Microsoft",
      "name": "System Application",
      "version": "27.0.0.0"
    },
    {
      "id": "xxxxxx",
      "publisher": "Microsoft",
      "name": "Base Application",
      "version": "27.0.0.0"
    }
  ],
  "screenshots": [],
  "platform": "28.0.0.0",
  "idRanges": [
    {
      "from": 50000,
      "to": 59999
    }
  ],
      "resourceExposurePolicy": {
    "allowDebugging": true,
    "allowDownloadingSource": true,
    "includeSourceInSymbolFile": true
  },
  "contextSensitiveHelpUrl": "xxxx",  
  "runtime": "17.0"
}

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

OussamaSabbouh 13,168 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Hello,

Use BC27 values when deploying to BC27 Production and BC28 values only when testing in the BC28 Preview sandbox: so yes, switch platform back to 27.0.0.0 for the v27 deployment, and also keep Base Application and System Application dependencies at 27.0.0.0; for BC27 use runtime: "16.0", and for BC28 use runtime: "17.0". Your app’s own "version" is just your extension version and does not need to match the BC version, so keep that on your normal release numbering. Easiest setup is one branch/workspace for BC27 production and another for BC28 preview testing, because a package targeted at 28 should not be published to 27.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Suggested answer

Rutvik Patel on at

Like (0)

Report
Copy link

Link copied!

Hi, There

You need to reduce the version to 27.0.0.0 otherwise it will give error.

if you found answer please mark it anwer

Thank You

Rutvik Patel

Was this reply helpful? Yes No
Suggested answer

Kamal Khakhkhar 2,969 on at

Like (1)

Report
Copy link

Link copied!

Hii there ,

for for requirement you need to go with max verison of current environment so for this you can try with less then 27. along with run time version 16.

as higher version is not allow to deploy directly .

please reduce application version and runtime version will Work.

if you found answer mark it answered.

Thank You.

Kamal Khakhkhar.

Was this reply helpful? Yes No

Join the conversation

Community site session details

App.json settings for compatibility fixing

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Meet the Microsoft Dynamics 365 Contact Center Champions

Congratulations to the March Top 10 Community Leaders

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates

Community site session details

App.json settings for compatibility fixing

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Meet the Microsoft Dynamics 365 Contact Center Champions

Congratulations to the March Top 10 Community Leaders

Subscribe to this forum!

Select categories

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates