# Upgrading Nodes specifically my own

**URL:** <https://discourse.nodered.org/t/upgrading-nodes-specifically-my-own/2641>\
**Category:** Developing Nodes\
**Created:** [28 August 2018 17:42 UTC](https://discourse.nodered.org/t/upgrading-nodes-specifically-my-own/2641 "2018-08-28T17:42:39Z")\
**Posts on this page:** 1\
**Showing post:** 11

<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:** [29 August 2018 19:54 UTC](https://discourse.nodered.org/t/upgrading-nodes-specifically-my-own/2641/11 "2018-08-29T19:54:34Z")

</div>

Hi Pete,

Seems I'm a bit too late to avoid you suffering from a programming burn-out 😉  
But here is how I try to add new properties to my contributions. Don't know if it is a correct design, but it seemed to be working fine ...

- A new input field is added to an existing node:

- To make sure it is stored (and communicated to the server-side), I add a newProperty with a default value 123 and a number validator:

- To get rid of the red triangle, you can apply a custom number validator:

- Another issue at this moment is that ( at the server-side ) the property also doesn't exist yet:

- As soon as the user opens the config screen of the node, you will see in the _oneditprepare_ that the _newProperty_ doesn't exist here yet (for existing nodes in your flow):

Hopefully this explains some things to you, and hopefully I didn't make things explode in your brain 😉  
Bart

---

_[View the full topic](https://discourse.nodered.org/t/upgrading-nodes-specifically-my-own/2641)._