OData V4 API and Credit Memos entity error

(0) Share

Report

Posted on by Community Member

HI,

We are using the OData V4 api of Business Central to get the info of some parts of the application and we found a situation that seems to be a bug in Dynamics.

If you access the endpoints for Sales Credit Memos (9302) or Purchase Credit Memos (9309) using the "select" statement in the request AND if you specify the "Accept" header with "application/json;odata.metadata=full", a http 500 error is thrown.

Here is an example:

Without the select statement, it works in both cases:

It seems to us like a problem inside the service.

Thanks!!

Categories:

Other

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Olister Rumao 4,009 on at

Like (0)

Report
Copy link

Link copied!

Hi Adrian,

Did you verify your wuery by going through the below URL?
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/webservices/use-filter-expressions-in-odata-uris
Although your query looks like a sql query. I suggest you can filter as per it is mentioned in the URL.

Thanks.

Was this reply helpful? Yes No
Suggested answer

Stefano Demiliani 37,166 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

This is a not supported url. Your second way is correct.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Olister,

I don't understand when you say that the query "looks like a sql query". In all cases the URLs follow the OData V4 standards and they fail only in the mentioned scenarios.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Stefano,

They URLs are correctly formed and they work in all the cases we tried except this two mentioned. And even in this two cases, they get to work when you don't specify the Accept header.

Was this reply helpful? Yes No