# UIBuilder Table Implementation 2.0

**URL:** https://discourse.nodered.org/t/uibuilder-table-implementation-2-0/80618
**Category:** Dashboard
**Tags:** uibuilder
**Created:** [16 August 2023 20:32 UTC](https://discourse.nodered.org/t/uibuilder-table-implementation-2-0/80618 "2023-08-16T20:32:47Z")
**Posts on this page:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [21 August 2023 00:47 UTC](https://discourse.nodered.org/t/uibuilder-table-implementation-2-0/80618/16 "2023-08-21T00:47:26Z")

</div>

Ah, right. I can see. The message you send back from your DB queries contains a msg.\_ui property already. But it isn't an array.

I think that is my fault. It is, of course, the output from the eventSend function and it is just an object not an array.

Perhaps I should have chosen a different msg property for the outputs.

Please delete the output msg.\_ui. Put a change node on the output from uibuilder. It should do 2 things. First, set `msg.button` (or some convenient property) to be `msg._ui.id`, then delete `msg._ui`. You can do that with a single change node.

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

NOTE: You may need to set the "deep copy" flag as shown above. Try without first.

Then your flow should work when you feed that into the `uib-element` node.

I have added a fix for the crash into the next release of uibuilder. I will also need to add a check to see if msg.\_ui.type exists - or maybe add another property to differentiate output \_ui properties from input ones.

Well done for finding an important bug in uibuilder 😁:

---

_[View the full topic](https://discourse.nodered.org/t/uibuilder-table-implementation-2-0/80618)._