The whole template will be updated with the msg properties. In you example, when msg.a
is undefined
then
<div>
<div>a: {{msg.a}}</div>
<div>b: {{msg.b}}</div>
</div>
will result :
This seems to be a reasonable and expected behavior, in my opinion.
I have updated msg.a
to undefined
, so I expect this reflected in the dashboard.
The bottom line is that it is necessary to add the required logic in the flow to craft the msg properties in the proper way. This is in line with what Colin suggested in his previous post (use a join node).