# Node-Red don´t set node properties default values on load

**URL:** <https://discourse.nodered.org/t/node-red-don-t-set-node-properties-default-values-on-load/41343>\
**Category:** Developing Nodes\
**Created:** [20 February 2021 10:51 UTC](https://discourse.nodered.org/t/node-red-don-t-set-node-properties-default-values-on-load/41343 "2021-02-20T10:51:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [20 February 2021 11:17 UTC](https://discourse.nodered.org/t/node-red-don-t-set-node-properties-default-values-on-load/41343/2 "2021-02-20T11:17:21Z")

</div>

Hi @iiot2k,  
Indeed when you afterwards add extra properties to a node, you simetimes need to add some extra code to make sure existing nodes don't fail. Because you need to make sure those nodes keep working fine in following circumstances:

1. When the config screen of an existing node is opened.
2. When the node runs without the config screen has been opened.

I have described my way of working [here](https://discourse.nodered.org/t/upgrading-nodes-specifically-my-own/2641/11). Hopefully that can answer some of your questions already.

Bart

---

_[View the full topic](https://discourse.nodered.org/t/node-red-don-t-set-node-properties-default-values-on-load/41343)._