# \[Django Admin Customization\] Avoid Overwriting Fields When Multiple Users Edit the Same Object

**URL:** <https://forum.djangoproject.com/t/django-admin-customization-avoid-overwriting-fields-when-multiple-users-edit-the-same-object/36920>\
**Category:** The Admin\
**Created:** [December 3, 2024, 11:08am UTC](https://forum.djangoproject.com/t/django-admin-customization-avoid-overwriting-fields-when-multiple-users-edit-the-same-object/36920 "2024-12-03T11:08:45Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![KenWhitesell](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/kenwhitesell/32/280_2.png) [@KenWhitesell](https://forum.djangoproject.com/u/KenWhitesell)\
**Post date:** [December 3, 2024, 1:50pm UTC](https://forum.djangoproject.com/t/django-admin-customization-avoid-overwriting-fields-when-multiple-users-edit-the-same-object/36920/2 "2024-12-03T13:50:47Z")

</div>

This topic was previously discussed at [Automatically setting update\_fields when saving a model instance](https://forum.djangoproject.com/t/automatically-setting-update-fields-when-saving-a-model-instance/26798), which includes an explanation of a situation where this would _not_ be desirable outcome.

In fact, while I do acknowledge the problem of a “lost update”, that is actually _less_ problematic to me than inconsistent data generated as a result of an incomplete update.

---

_[View the full topic](https://forum.djangoproject.com/t/django-admin-customization-avoid-overwriting-fields-when-multiple-users-edit-the-same-object/36920)._