# Proposed changes to last-saved functionality

**URL:** <https://forum.getodk.org/t/proposed-changes-to-last-saved-functionality/41153>\
**Category:** Ideas\
**Tags:** odk-collect\
**Created:** [April 13, 2023, 3:55pm UTC](https://forum.getodk.org/t/proposed-changes-to-last-saved-functionality/41153 "2023-04-13T15:55:11Z")\
**Posts on this page:** 2\
**Page:** 1

<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:** [April 13, 2023, 3:55pm UTC](https://forum.getodk.org/t/proposed-changes-to-last-saved-functionality/41153/1 "2023-04-13T15:55:11Z")

</div>

We have evaluated and experimented with the [last-saved functionality](https://docs.getodk.org/form-logic/#values-from-the-last-saved-record) for several different uses cases. It is already quite helpful for streamlining the experience for enumerators, however, I believe a couple (hopefully small) changes would make it more broadly useful within our project:

1. If possible, it would be helpful to keep last-saved# values across form updates. Right now, when a form update is released, any last-saved# values from previous iterations of the form are lost. (I believe there is an older discussion about this on the forum somewhere, but I'm afraid I could not find it just now.)
2. We plan to use encrypted forms, but would still like to use last-saved#. Would it be possible (and desirable) to support last-saved#, even for encrypted forms? That being said, not storing anything other than the last-saved# values would be preferable, if possible. A caveat in the documentation might read something like, "If your project is using encrypted forms, please note that last-saved# values will be stored in an unencrypted state so that they can be used on future iterations of the form. Sensitive values should not be accessed via last-saved#."

Thank you as always for your feedback!

---

<div class="post-metadata">

**Author:** ![LN](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/ln/32/1605_2.png) [@LN](https://forum.getodk.org/u/LN)\
**Post date:** [April 24, 2023, 10:00pm UTC](https://forum.getodk.org/t/proposed-changes-to-last-saved-functionality/41153/2 "2023-04-24T22:00:58Z")

</div>

> [@TobiasMcNulty](#):
>
> would be helpful to keep last-saved# values across form updates

[Deactivate option if selected once - #4 by LN](https://forum.getodk.org/t/deactivate-option-if-selected-once/38221/4) is where we discussed this last. The schema that was last saved could possibly be incompatible with a query in the form but in that case a blank value would be returned. We'll try to schedule this one soon.

> [@TobiasMcNulty](#):
>
> not storing anything other than the last-saved# values would be preferable

This would require some preprocessing of forms that's not currently done.

As of [Collect v2024.1](https://forum.getodk.org/t/odk-collect-v2024-1/45170), last-saved values are kept across form updates. We are not currently planning to store last-saved values for encrypted submissions.
