As I updated the model, it throws "Does not support untyped value in non-open type". It was working before the update. Unable to pin down the source of the problem. any ideas.
相关问题
- Design RESTful service with multiple ids
- Axios OPTIONS instead of POST Request. Express Res
- Plain (non-HTML) error pages in REST api
- POST Base64 encoded data in PHP
- Laravel 5.1 MethodNotAllowedHttpException on store
相关文章
- odata怎么开启括号查询
- Got ActiveRecord::AssociationTypeMismatch on model
- Multiple parameters in AngularJS $resource GET
- Global Exception Handling in Jersey & Spring?
- REST search interface and the idempotency of GET
- Getting error detail from WCF REST
- Send a GET request with a body in JavaScript (XMLH
- GuzzleHttp Hangs When Using Localhost
I've experienced this error before and it's caused by passing a property of a JSON object that doesn't exist on the data model.
For example, given the data model:
And an OData controller has the method:
When the following data is sent using the
POST
method:Then the server will return error 400 with with the following response:
So if the
UserPassword
property, in this example, is removed from the data sent using thePOST
method, then the error doesn't occur.