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

Error while uploading the extension as PTE.

(7) Share

Report

Posted on by CU03020606-0

This is my app.json.

{
  "id": "xxxxx",
  "name": "xxxxx",
  "publisher": "xxxxx",
  "version": "xxxxx",
  "brief": "",
  "description": "",
  "privacyStatement": "",
  "EULA": "",
  "help": "",
  "url": "",
  "logo": "",
  "dependencies": [
    {
      "id": "ec255f57-31d0-4ca2-b751-f2fa7c745abb",
      "name": "Shopify Connector",
      "publisher": "Microsoft",
      "version": "27.3.44313.44979"
    }
  ],
  "screenshots": [],
  "platform": "1.0.0.0",
  "application": "27.0.0.0",
  "idRanges": [
    {
      "from": 50000,
      "to": 54100
    }
  ],
  "resourceExposurePolicy": {
    "allowDebugging": false,
    "allowDownloadingSource": false,
    "includeSourceInSymbolFile": false
  },
  "runtime": "16.0",
  "features": [
    "NoImplicitWith"
  ]
}

In one of the environment it got uploaded as PTE but in another two environments i got errors.
Both the environment are latest version.

Error:
Deploy Operation rejected. Error: Error parsing version string:. Path 'value[3].applicationDependencyVersion', line 1, position 2839.; - Job Id : 30697227-cddd-4144-b23f-cd7fea16ae74

can someone help me solve this thing.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (9)

Answers (0)

Sort by

Suggested answer

Nitin Verma 21,794 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi,

Can you check if you have dependency app version the same you are referring in app file?

Thanks.

Was this reply helpful? Yes No
CU03020606-0 67 on at

Like (0)

Report
Copy link

Link copied!

Yup its exactly same.
I already checked the version they are the same.

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 13,323 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hello,

That error basically means BC is reading an empty/invalid version string during deploy (it literally says it failed to parse applicationDependencyVersion and the value is blank). Fix is to ensure every version you ship is a valid version format (Microsoft expects W.X.Y.Z numeric for app/version properties and dependency versions), and that your actual uploaded .app really contains those values (watch out for CI/CD tokens like $(BuildVersion) resolving to empty in some pipelines). Also double-check the target environments have the Shopify Connector installed and healthy (same publisher/name, and a real numeric version), because dependency resolution uses the dependency’s minimum version rule and will fail if the tenant’s dependency metadata is broken/missing.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 99,324 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Do you encounter this problem when you create a new Hello World extension?
I just tried it and it worked fine in my environment.

Thanks.

ZHU

Was this reply helpful? Yes No
Suggested answer

Dhiren Nagar 2,898 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hi,

Can you prepare a fresh project and try to deploy? Also instead of writing exact versions in the dependency you can write 27.0.0.0.

Clear cache, download fresh symbols, compile and deploy.

✅ Tick the checkbox below to mark the answer as verified, if it helped resolve your question.

Regards,

Dhiren.

LinkedIn - https://www.linkedin.com/in/ca-dhiren-nagar-5079081b2/

Blog - https://dhirennagar.blogspot.com/

Was this reply helpful? Yes No
Suggested answer

Touil Yahya 220 on at

Like (1)

Report
Copy link

Link copied!

Hi,

In most cases, this error occurs because the version of the Shopify Connector installed in the target environment does not match the version specified in your app.json.

What you should do

Update the dependency version to a broader compatible version, for example:

{
"id": "ec255f57-31d0-4ca2-b751-f2fa7c745abb",
"name": "Shopify Connector",
"publisher": "Microsoft",
"version": "27.0.0.0"
}

Then:

Recompile the extension

Redeploy it to the target environment

Was this reply helpful? Yes No
CU02041247-0 2 on at

Like (0)

Report
Copy link

Link copied!

MS Suggests removing any designer app to make it work. But it did not resolve the issue.

Was this reply helpful? Yes No
Suggested answer

RockwithNav 8,991 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

This is known error. Hopefully MS will fix sooner than later.

Was this reply helpful? Yes No
CU03020606-0 67 on at

Like (0)

Report
Copy link

Link copied!

Hey Everyone,

Thanks for your support. It was a microsoft internal error and was happening because of postponed upgrade 27.4. Now its working fine.

Was this reply helpful? Yes No