Conflict Resolution - Object User Edited No Longer Exists in Latest Backing Dataset

Ask the Community
1

Hi all I have a snapshot backing dataset for an object, and I’ve enabled user edits. If the user edits an object, and then afterwards the backing dataset is built and no longer includes that object (i.e., there is no object with the UID that was on the object the user edited), what happens in the ontology layer / in the materialized dataset that includes user edits? I want to assume that the object will disappear along with the user’s edits in both the object and in the materialized dataset. Is that correct? Thanks

2

You are correct that when an object with a particular primary key is removed from the backing dataset, it is also removed from the final object state. However, the edits themselves aren’t lost. So if the object with that primary key re-appears in the backing dataset, the final object state will include any previously applied edits. The example in the documentation outlines in more detail how the “user edit wins” strategy works in conjunction with changes to the backing dataset, assuming that’s the strategy you’ve enabled for your object type.

1 Like
3

Thanks @cdesouza. If you have “apply latest version” strategy, then the the previously applied user edits will disappear forever – even if the object with that primary key reappears in the backing dataset, right?

4

Hi @hweinstein - if “apply latest version” is enabled, the user edits are conditionally applied depending on:

  • The timestamp property that you’ve configured for conflict resolution - user edits are applied only if the timestamp associated with the edits is more recent than the value of the timestamp property.
  • Whether you’ve configured any properties to be edit only - user edits are applied to these properties regardless of the value of the timestamp property