jaydata
jaydata copied to clipboard
Cannot update key fields using odata
When using odata, it is impossible to update a key field. The URL is constructed based on the current values in the entity, so if one of the key fields has changed, the MERGE request will result in a 404 Not Found error.
The odata server is nice enough to include a URI in the metadata of the entity. Why not use that instead of reconstructing the URL every time?
Yes, updating key fields is disallowed by odata, but 404 is not the right error message, and it should really be left to the provider to determine what to do.