# Bug with update dashboard-2 version 1.23

**URL:** <https://discourse.nodered.org/t/bug-with-update-dashboard-2-version-1-23/96911>\
**Category:** Dashboard\
**Tags:** dashboard-2\
**Created:** [5 May 2025 18:28 UTC](https://discourse.nodered.org/t/bug-with-update-dashboard-2-version-1-23/96911 "2025-05-05T18:28:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![SergioRT](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sergiort/32/19289_2.png) [@SergioRT](https://discourse.nodered.org/u/SergioRT)\
**Post date:** [5 May 2025 18:28 UTC](https://discourse.nodered.org/t/bug-with-update-dashboard-2-version-1-23/96911/1 "2025-05-05T18:28:19Z")

</div>

After installing flowfuse dashboard-2 version 1.23, the following bugs appeared:

- On a dropdown node, when you clear the selection with the cross, no messages appear. It is therefore impossible to detect this clearing action.
- With the tabulator node, when a row is selected, normally, msg.topic takes the value "tbNotification." After the update, msg.topic took the value "undefined."

After downgrading to version 1.22.1, these two bugs have been fixed.

---

<div class="post-metadata">

**Author:** ![omrid](https://avatars.discourse-cdn.com/v4/letter/o/77aa72/32.png) [@omrid](https://discourse.nodered.org/u/omrid)\
**Post date:** [5 May 2025 22:15 UTC](https://discourse.nodered.org/t/bug-with-update-dashboard-2-version-1-23/96911/2 "2025-05-05T22:15:06Z")

</div>

> [@SergioRT](#):
>
> With the tabulator node, when a row is selected, normally, msg.topic takes the value "tbNotification." After the update, msg.topic took the value "undefined."

This is a general bug in dashboard-2 v1.23, also happening in `template` nodes. Every message sent as a `widget-action` (which is what `ui-tabulator` uses for notifications) is overwritten by the dashboard framework which sets `msg.topic` to `undefined`.

This has been raised as issue [#1683](https://github.com/FlowFuse/node-red-dashboard/issues/1683), and the dashboard development team is aware of it.

for now you will need to stay with dashboard 1.22.1 until this issue is fixed.

---

<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:** [4 June 2025 22:15 UTC](https://discourse.nodered.org/t/bug-with-update-dashboard-2-version-1-23/96911/3 "2025-06-04T22:15:53Z")

</div>

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