-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change related entity with PUT #1994
base: main
Are you sure you want to change the base?
Conversation
Example ##ex: When updating an entity with a 4.01 `PUT` request, the target of a | ||
non-containment navigation property can be replaced without changing either the | ||
old or the new targeted entity itself. The targeted entity can then only be | ||
specified by an entity reference (see [OData-JSON, section "Entity Reference"]($$$OData-JSON$$$#EntityReference)): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"specified as"?
"@context": "$metadata#$ref", | ||
"@id": "Employees(6)", | ||
"EmployeeID": 6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is not a valid entity reference, additional properties are not allowed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you remove the @context
, it becomes an incomplete entity and a valid example for undesired effects.
Suggestion from @GEricson: use two-column table, with request on the left and resulting entities in the right column. |
|
Fixes #1973