Open patrick-werner opened 3 years ago
Describe the bug When sending a transaction to the current hapi jpastarter (5.3.0) hapi changes the order of the request.
{ "resourceType": "Bundle", "type": "transaction", "entry": [ { "request": { "method": "DELETE", "url": "Observation?_has:DiagnosticReport:result:_id=24471" } }, { "request": { "method": "DELETE", "url": "/List?code=C115916&subject=5016" } }, { "request": { "method": "DELETE", "url": "DiagnosticReport/24471" } } ] }
I expected, that the order of the entries would be the order of execution. But hapi first deletes the DR, and then fails to delete the Observations.
To Reproduce Steps to reproduce the behavior:
Expected behavior HAPI deletes the observations AND the DiagnosticReport
Environment (please complete the following information):
Zulip Thread: https://github.com/hapifhir/hapi-fhir/issues/2501
Describe the bug When sending a transaction to the current hapi jpastarter (5.3.0) hapi changes the order of the request.
I expected, that the order of the entries would be the order of execution. But hapi first deletes the DR, and then fails to delete the Observations.
To Reproduce Steps to reproduce the behavior:
Expected behavior HAPI deletes the observations AND the DiagnosticReport
Environment (please complete the following information):