Yeah, this definitely works, thank you for the suggestion!

It just requires always have an additional API call to read the current state and sending the full object definition back and forth on any single attribute update.
What defeats the purpose of having the PATCH method that exists specifically to avoid this.

A proper patch implementation would require a different ObjectMapper without JsonInclude.Include.NON_NULL and keeping WRITE_NULL_MAP_VALUES in the default true state.

Hi there!

I'm using the Java client library and want to call the patchUser() method.
The API documentation suggests to use nulls to clean up currently assigned field values. But the client implementation uses an internal objectMapper that seems always skips nulls. I don't see an option to provide my own object mapper.
To add a bit more details - I need to clean up some attributes and sub-sections of the data map.

Any suggestions how to use patches in such cases?

Thank you!