Incorrect record_id in endpoints url - inconsistent error messages

Pawel Bartkowiak
2026-03-31T14:44:19Z

* record_id at Url level
* test case wrong data partition id:
* return incorrect error message: it consists of 2 error codes and it is not formatted json inside of main reason key.
* test cases wrong data partition id and non-existing record_id:
* post data endpoint is inconsistent vs all other endpoints using record_id at url level
* as post data API returns inconsistent to other response:{\
"code":422,\
"reason":"Data validation failed.",\
"errors":{"Missing records in storage":\["osdu:work-product-component--SaturationFunctionSet:NonExistingID"\]}}
* while others: {\
"code": 404,\
"reason": "Record not found",\
"message": "The record 'osdu:work-product-component--SaturationFunctionSet:Test123:' was not found"}
* record_id at body request for post record API:
* test case wrong data partition id:
* shouldn't status code be also 422 not 400?
* record_id at body request for post data API:
* As there is already following defect: #678**,** so maybe worth focusing on errors for this endpoint, as any differences vs record_id in url should be treated with separate type of error message and fixed under #678

[Record_id wrong values investigation.xlsx](/uploads/9436ba7082a0ea5be9d48adc6e273994/Record_id_wrong_values_investigation.xlsx)