# Node config parameter not following default value

**URL:** <https://discourse.nodered.org/t/node-config-parameter-not-following-default-value/83393>\
**Category:** Developing Nodes\
**Created:** [2 December 2023 21:03 UTC](https://discourse.nodered.org/t/node-config-parameter-not-following-default-value/83393 "2023-12-02T21:03:26Z")\
**Posts on this page:** 1\
**Showing post:** 15

<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:** [3 December 2023 22:59 UTC](https://discourse.nodered.org/t/node-config-parameter-not-following-default-value/83393/15 "2023-12-03T22:59:32Z")

</div>

> [@danube](#):
>
> Now these default values are present if the node is being newly created from the palette

Hi @danube,  
Indeed when you add a new property to a node, that won't exist on existing nodes. So you always have to deal with 2 cases:

- html file: When the user opens the config screen of such an old node, you have to set explicit (with a js statement) the default value if the property does not exist yet, and show that default value.
- js file: When the user does _NOT_ open the config screen, then the backend of your code also needs to set the default value if the property does not exist yet. To make sure that existing nodes process input messages correctly.

See more info [here](https://discourse.nodered.org/t/upgrading-nodes-specifically-my-own/2641/11).

Bart

---

_[View the full topic](https://discourse.nodered.org/t/node-config-parameter-not-following-default-value/83393)._