You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In MyCarePlanner, when performing a DELETE operation against the SDS, the DELETE may return either 200 OK or 409 Conflict.
When the DELETE operation returns 409 Conflict, it means that there are more resources in the SDS that should be marked deleted, but which haven't been so marked.
This is easy to resolve, by following the following logic:
HttpResponse response = null;
while (response == null OR response.code == 409) {
response = execute_delete_operation_for_patient;
}
Since the DELETE operation won't process previously-deleted resources, each execution of the DELETE operation against a particular Patient will cause more of the Patient's resources to be marked deleted, until, eventually, with enough successive executions of the request, they will all be marked deleted. At that time, the SDS will return 200 OK.
The text was updated successfully, but these errors were encountered:
In MyCarePlanner, when performing a DELETE operation against the SDS, the DELETE may return either
200 OK
or409 Conflict
.When the DELETE operation returns
409 Conflict
, it means that there are more resources in the SDS that should be marked deleted, but which haven't been so marked.This is easy to resolve, by following the following logic:
Since the DELETE operation won't process previously-deleted resources, each execution of the DELETE operation against a particular Patient will cause more of the Patient's resources to be marked deleted, until, eventually, with enough successive executions of the request, they will all be marked deleted. At that time, the SDS will return
200 OK
.The text was updated successfully, but these errors were encountered: