# The \`change\` node..... Checking what I expect to what it does

**URL:** <https://discourse.nodered.org/t/the-change-node-checking-what-i-expect-to-what-it-does/20829>\
**Category:** General\
**Created:** [25 January 2020 02:49 UTC](https://discourse.nodered.org/t/the-change-node-checking-what-i-expect-to-what-it-does/20829 "2020-01-25T02:49:57Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [25 January 2020 12:42 UTC](https://discourse.nodered.org/t/the-change-node-checking-what-i-expect-to-what-it-does/20829/12 "2020-01-25T12:42:17Z")

</div>

I can understand why it looks wrong at first glance

But at present time, we can move the payload to a sub-property and the change node does it.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/f/3/f3814eccada5bb43c2c8a104b5451d36ed8a9f82.png)

So I think the behaviour of ignoring non object type and just doing it is already in use.

[edit]  
@zenofmud has found previous reference

> [@How to send a picture through Telegram?](https://discourse.nodered.org/t/how-to-send-a-picture-through-telegram/20327/21):
>
> to be fair - that is indeed (yet another) a subtlety of javascript. If the object is an object it's easy to add/edit/remove properties. If it's a type like a number or string (or boolean) then that can't be assigned extra properties so trying to add them will fail.

---

_[View the full topic](https://discourse.nodered.org/t/the-change-node-checking-what-i-expect-to-what-it-does/20829)._