# Deactivate option if selected once

**URL:** <https://forum.getodk.org/t/deactivate-option-if-selected-once/38221>\
**Category:** Support\
**Tags:** form-design, odk-collect\
**Created:** [July 6, 2022, 1:17pm UTC](https://forum.getodk.org/t/deactivate-option-if-selected-once/38221 "2022-07-06T13:17:03Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![TobiasMcNulty](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/tobiasmcnulty/32/19773_2.png) [@TobiasMcNulty](https://forum.getodk.org/u/TobiasMcNulty)\
**Post date:** [February 9, 2023, 4:19pm UTC](https://forum.getodk.org/t/deactivate-option-if-selected-once/38221/6 "2023-02-09T16:19:20Z")

</div>

> [@LN](#):
>
> > [@ahblake](#):
> >
> > Updating the definition will clear the last saved value on Collect
> 
> I don't think there's a strong reason for this and I'm becoming more and more convinced that it's confusing and dangerous.

We are employing a similar workaround for detecting and preventing on-device duplicates (building up a list of `last-saved` values), but `last-saved` being cleared at form update is a challenge for us (and has certainly led to some personal confusing when testing locally, before I remembered how this works 😅).

Is there some consensus around changing this behavior? If so, is it small enough (and not too disruptive) that it could reasonably be included in an upcoming release?

---

_[View the full topic](https://forum.getodk.org/t/deactivate-option-if-selected-once/38221)._
