Tom Frenken

Hi @AdrianRygiol, thank you for your feedback. If I search for your exact use case of local destinations, I immediately find [this entry](https://sap.github.io/cloud-sdk/docs/js/features/connectivity/destinations#local-environment-variable) in our documentation, do you feel like...

After reading through the documentation that you've linked, I can see how that can be confusing, I will create a PR to update this specific part of our documentation.

Hey @seeroush thank's for reaching out. The usage of the SDK does look correct, and the empty patch request is rather suspicious. Also, the fact that[ CSRF fetching](https://sap.github.io/cloud-sdk/docs/js/features/connectivity/csrf#default-behaviour) as well...

Hmm, let's try a few things. 1) We read the `etag` from the response. The selection process for the appropriate `etag` looks like this: ``` const eTag = extractEtagFromHeader(response.headers) ||...

The issues you are currently facing should be unrelated to the cloud connector. Can you share for which service you've generated the client? That way I can generate it myself...

Alright, I've generated a client and tried to replicate the issue, however, for me, the correct payload was created. My current assumption is, that the remote state has been updated...

Alternatively, you can also try to use a `PUT` request instead, as [documented here](https://sap.github.io/cloud-sdk/docs/js/features/odata/v2-client#replace-the-entity-with-put). This should definitely contain your change, as it doesn't depend on the remote state.

Hi @ElectronicWizzard, a workaround for this is implied in the error message; you can convert the automatically generated certificates with the described tool and/or a library of your choice. I've...