This would be really useful, and seems a very obvious missing feature. Any ideas when this might happen? I've got potential issues if other users are standard saving a record in between the GET and PUT requests of another user; even if they've only edited a different field to the API their edits will be overwritten by the PUT request which of course has to PUT all the form_values, even if the API is only changing one field's value.

Bumping, this would be great

this is really really needed. Or allow a PUT with a subset and only update the subset.

I specifically want to be able to PATCH a subset of field attributes, while leaving the other attributes unmodified.

A little context as to why this is helpful.

My company is in the agricultural space. We do in-field measurements for our customers.

We have a web-app that is our system of record for "what measurements do we need to do?" Any time a record is changed on our system, we push it to Fulcrum, e.g. we change the type of measurements required, we add some notes about the measurement, and so on.

In an ideal world, I would like to push an updated note. However, that is not possible. So instead, I am running into a situation where I can do a data collision. Consider the following.

Of course, there is a work-around. Before any update call, my app could fetch the current state of a record, do a merge of attributes, and then post the final update. HOWEVER, this is the exact purpose of a PATCH request in a RESTful API.