# Save/restore state of dashboard input elements

**URL:** <https://discourse.nodered.org/t/save-restore-state-of-dashboard-input-elements/41685>\
**Category:** Dashboard\
**Created:** [26 February 2021 17:08 UTC](https://discourse.nodered.org/t/save-restore-state-of-dashboard-input-elements/41685 "2021-02-26T17:08:44Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Paul-Reed](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/paul-reed/32/66906_2.png) [@Paul-Reed](https://discourse.nodered.org/u/Paul-Reed)\
**Post date:** [26 February 2021 19:15 UTC](https://discourse.nodered.org/t/save-restore-state-of-dashboard-input-elements/41685/2 "2021-02-26T19:15:48Z")

</div>

> [@pacosta](#):
>
> When the user changes the state manually, or via an input message, that state would be saved in the global file context

Yes, node persistence has been discussed previously, and slowly but surely many of the contrib nodes are adding this as an option.  
It's something that I have raised a while ago, see [❓ DISCUSSION: Should nodes save/restore their own context?](https://discourse.nodered.org/t/discussion-should-nodes-save-restore-their-own-context/20590)

> [@pacosta](#):
>
> but I have not looked at the other nodes to see if this can be extended to all the other input widgets.

I believe that the developers have previously said that they would want some form of consistency across the relevant nodes, instead of being implemented piecemeal.

> [@pacosta](#):
>
> I may also be missing important implications or ramifications of this proposal

Isn't there always 😉

I think that I've found your repo (Dr. Pablo Acosta?), but not your PoC. It would be great to know more about your proposal, and more detail of how you see it working.

Thanks for posting.

---

_[View the full topic](https://discourse.nodered.org/t/save-restore-state-of-dashboard-input-elements/41685)._