# Store and Restore dynamic node UI properties

**URL:** <https://discourse.nodered.org/t/store-and-restore-dynamic-node-ui-properties/66831>\
**Category:** Developing Nodes\
**Created:** [24 August 2022 05:37 UTC](https://discourse.nodered.org/t/store-and-restore-dynamic-node-ui-properties/66831 "2022-08-24T05:37:40Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [24 August 2022 08:45 UTC](https://discourse.nodered.org/t/store-and-restore-dynamic-node-ui-properties/66831/5 "2022-08-24T08:45:49Z")

</div>

> [@mbenson](#):
>
> What is the mechanism that Node Red uses to identify data it needs to persist? Something I’m doing with dynamically generating the properties is making it not persist. When I click save, close the dialog, and reopen it, my dynamic properties are back to empty. Is there anything I can do to ensure they persist? Or am I bending Node Red too far?

This might help..

> [@I added input feilds dynamically then how can i save data from those inputs in the defaults](https://discourse.nodered.org/t/i-added-input-feilds-dynamically-then-how-can-i-save-data-from-those-inputs-in-the-defaults/62687/4):
>
> By the looks of it, your custom node is not using the dedicated [editableList](https://nodered.org/docs/api/ui/editableList/) I would suggest you look at the source of any of the built in nodes that have an editableList for reference. In short, you need to loop through the entries in oneditsave and store them as an object or array in the defaults. See here for more info: [Node edit dialog : Node-RED](https://nodered.org/docs/creating-nodes/edit-dialog)

---

_[View the full topic](https://discourse.nodered.org/t/store-and-restore-dynamic-node-ui-properties/66831)._