# A question about using ui\_update in Dashboard 2

**URL:** <https://discourse.nodered.org/t/a-question-about-using-ui-update-in-dashboard-2/89221>\
**Category:** Dashboard\
**Tags:** dashboard-2\
**Created:** [3 July 2024 10:44 UTC](https://discourse.nodered.org/t/a-question-about-using-ui-update-in-dashboard-2/89221 "2024-07-03T10:44:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [3 July 2024 10:44 UTC](https://discourse.nodered.org/t/a-question-about-using-ui-update-in-dashboard-2/89221/1 "2024-07-03T10:44:42Z")

</div>

If I use `msg.ui_update` to modify one of the core node's properties is there a way of getting back to the original property setting other than restarting? I ask because, as I understand it, ui\_update is not automatically available to third party ui nodes so I am emulating the core node operation in my node and want to make sure that it operates in the same way as it does in the core nodes.

---

<div class="post-metadata">

**Author:** ![joepavitt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/joepavitt/32/59722_2.png) [@joepavitt](https://discourse.nodered.org/u/joepavitt)\
**Post date:** [3 July 2024 11:05 UTC](https://discourse.nodered.org/t/a-question-about-using-ui-update-in-dashboard-2/89221/2 "2024-07-03T11:05:48Z")

</div>

Currently, no there isn't, but we do maintain the states separately on the server-side, so it's something we _could_ support/introduce

---

<div class="post-metadata">

**Author:** ![joepavitt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/joepavitt/32/59722_2.png) [@joepavitt](https://discourse.nodered.org/u/joepavitt)\
**Post date:** [3 July 2024 11:06 UTC](https://discourse.nodered.org/t/a-question-about-using-ui-update-in-dashboard-2/89221/3 "2024-07-03T11:06:55Z")

</div>

> [@Colin](#):
>
> ui\_update is not automatically available to third party ui nodes

RE; this statement, it's a best practice that we can't really _enforce_ for third-party nodes. We've just built the core nodes to be consistent in this pattern

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [3 July 2024 11:11 UTC](https://discourse.nodered.org/t/a-question-about-using-ui-update-in-dashboard-2/89221/4 "2024-07-03T11:11:02Z")

</div>

> [@joepavitt](#):
>
> RE; this statement, it's a best practice that we can't really _enforce_ for third-party nodes.

I meant that there is not (as far as I know) any help given to third party nodes to handle ui\_update, so I have to provide it all myself. Not that there is any problem doing that, it is easy I think.

> [@joepavitt](#):
>
> we do maintain the states separately on the server-side, so it's something we _could_ support/introduce

OK, I will do the same then so that I have the possibility of remaining compatible. Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [2 August 2024 11:11 UTC](https://discourse.nodered.org/t/a-question-about-using-ui-update-in-dashboard-2/89221/5 "2024-08-02T11:11:39Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.