Location Update does return bad request when location not found

[Florian Haase]

Hi

the Location endpoint returns a bad request code when we run a put and the location was not found.

Return-Message:

"{\"message\":\"Location 7080000065264 of bAccount 80001 not found\"}"

StatusCode = 400

All the other endpoints returns a Not Found Status code (404)

Not sure whats actually correct since 404 actually means that the resource does not exist per definition of this code.

But we use this statuscode to run a post after the put to create the record instead of update. This is implemented generic so it makes trouble if the statushandling is not the same for the endpoints. 

Florian

[Yıldırım]

Hello Florian, 

this case has been resolved but not released yet. Since it is a breaking change, we've shared the notice period and information about the planned date. Details can be seen here [Due dates for breaking changes].

[Yıldırım]

Hello, 

we'll check with the team whether this was an intended response returned correctly in the PUT request and inform the community accordingly.