Editing together leads to overwriting the changes

[Pete_Bush]

I have encountered the following problem:

In an app, different departments need to enter information about a case. These are not defined in a sequence so it happens that users work on the same case. If user 1 saves the information for his department in field A and then user 2 saves the information for his department in field B, the information in field A is set to empty again.

It seems to be the case that even if only field B is edited the whole row is beeing updated and since the field A (even if not even available to edit for User B) is not yet synced and therfore empty the field gets overwriten with empty.

This leads to a lot of frustation. Is there any way to just edit the field instead of the whole row or to be sure that every user can only work with the updated information (something like user 2 cannot save out of sync information) 

[Aurelien]

Hi @Pete_Bush 

In my humble opinion, the best you could try it to turn these options this way.

[Pete_Bush]

Hi @Aurelien 

Thanks for your reply

Sadly, I alread have theese settings like u suggested.

[Aurelien]

Unfortunately, co-edition through the app is basically not possible.

These settings will allow to have the freshest possible information when editing, but every record is updated on a row, so there is no focus on one column specifically.

Any workaround would be tedious to implement, in my opinion.

[Steve · Accepted solution]

---

@Pete_Bush wrote:

It seems to be the case that even if only field B is edited the whole row is beeing updated and since the field A (even if not even available to edit for User B) is not yet synced and therfore empty the field gets overwriten with empty.

---

That is exactly what's happening.

You need to structure your data differently, there's simply no way around it.