OData / OData/odataorg.github.io
Value cannot be null. Parameter name: edmEntityObject
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 73
- Forks
- 106
- PR merge metrics
- No merged PRs in 30d
Description
When I try to create a Create a Derived Entity with the data given in Tripin Advanced Usages, am getting the following error.
{
"error": {
"code": "",
"message": "Value cannot be null.\r\nParameter name: edmEntityObject"
}
}
Data sent via postman:
header:
{
Content-Type: application/json
}
{
"@odata.type": "Microsoft.OData.Service.Sample.TrippinInMemory.Models.Manager",
"UserName": "mirsking",
"FirstName": "Mirs",
"LastName": "King",
"AddressInfo": [
{
"Address": "Microsoft",
"City": {
"Name": "Shanghai",
"CountryRegion": "China"
}
}],
"BossOffice":{
"Address": "Microsoft",
"City": {
"Name": "Shanghai",
"CountryRegion": "China"
}
},
"Budget": 100
}
Please advise what I am doing wrong.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the TripPin Advanced Usages example and compare its derived-entity request with the JSON sent through Postman. Reproduce the request against the referenced service and determine whether the null edmEntityObject error is caused by the payload or the service; done means identifying the required correction or confirming a service defect.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100