Hi,
we are very frequently stumbling across a missing functionality, which is the reset/discard user edits on object types.
Imagine, you have an object type that is backed by a backing dataset. It has a property that frequently updates via pipeline, but you want to allow users to edits that value. The underlying dataset is still frequently updating the value, but since it has an ontology edit, only that edit is valid - so far so good.
Now imagine the case, the user wants to reset that edit (discard) and let again the value be defined by the frequently-updating backing dataset value.
As per my understanding, there is actually no direct way of achieving such a discard. In situations where we can not prevent the discard case, we are implement a very effortfull workaround
This is: we store edits which potentially require reset in separate object types additionally. When the user applies an edit, we edit the main object type and create the secondary „edited property" object. With every pipeline build, we actually use again the edited property objects to set those values again in pipeline. We have to do this, so since it requires the conflict resolution of the object type to be „most recent" . This is very annoying, since it requires a latest timestamp property which updates with every build. Meaning also, the full object type indexes completely with every build, since the timestamp property updated . If you try to be cost-aware this is not helping 
Not sure if I am missing something. Do others phase a similar issue?
Edit: also found this doc section stating that this functionality does not exist. Really wondering why such a functionality does not yet exist.
https://www.palantir.com/docs/foundry/object-edits/how-edits-applied/
