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

DeltaLink with DeltaToken fails

(0) Share

Report

Posted on by TT999

The BC API v2 returns http/500, and content: "{"error":{"code":"Unknown","message":"Internal Server Error. (500) "}}", when using a deltalink, returned from a previous "odata.track-changes".
The original query:
api.businesscentral.dynamics.com/.../customers
with header:
request.Headers.Add("Prefer", "odata.track-changes");
returns the deltalink:
api.businesscentral.dynamics.com/.../customers

Which produces the http/500
HttpMethod GET, version "1.1"
ConfidentialClient authentication

Any ideas, anyone?

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Andy Sather on at

Like (0)

Report

Hello,

If you don't get further responses to this issue, you may want to raise a support request to Microsoft support via your CSP / Partner.

Was this reply helpful? Yes No
YUN ZHU 95,649 Super User 2025 Season 2 on at

Like (0)

Report

Hi, maybe the entity you are using may not support delta tokens.

https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-connect-apps-delta#delta-support-limitations

Hope this helps.

Thanks.

ZHU

Was this reply helpful? Yes No
TT999 5 on at

Like (0)

Report

Thank you for replying.

I may be wrong, but I am under the impression that the standard customers API allows delta tokens.

At least the property "ChangeTrackingAllowed" is true in page 30009 "APIV2 - Customers".

And the http/500 does not occur on the deltalink request. The delta link is returned, but fails when used.

Was this reply helpful? Yes No
TT999 5 on at

Like (0)

Report

In anyone else struggles with this:
I opened a support request against Microsoft. And they have "acknowledged the situation", and will create a hotfix.
Which will be deployed after "up to 6 weeks".

Was this reply helpful? Yes No
TT999 5 on at

Like (0)

Report

Thank you, I did just that.

And they will be releasing a fix.

Was this reply helpful? Yes No