# Newly refreshed dashboard table shows stale data after all dashboards closed for some time **URL:** \ **Category:** Dashboard\ **Created:** [15 August 2021 04:03 UTC](https://discourse.nodered.org/t/newly-refreshed-dashboard-table-shows-stale-data-after-all-dashboards-closed-for-some-time/49730 "2021-08-15T04:03:17Z")\ **Posts on this page:** 1\ **Showing post:** 4

**Author:** ![Christian-Me](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/christian-me/32/10774_2.png) [@Christian-Me](https://discourse.nodered.org/u/Christian-Me)\ **Post date:** [13 September 2021 05:23 UTC](https://discourse.nodered.org/t/newly-refreshed-dashboard-table-shows-stale-data-after-all-dashboards-closed-for-some-time/49730/4 "2021-09-13T05:23:56Z")

Perhaps this post give you a starting point: > [@Problem with data displayed in UI-Table when switching Tabs](https://discourse.nodered.org/t/problem-with-data-displayed-in-ui-table-when-switching-tabs/48940/7): > > So something like a logfile .... This is using a little bit more complex (but universal) subflow I use for all my tables. But you can do it more simple too: A) a function node which gets an array (of lines) from the flow context and pushes the new line at the end B) a second function node triggered by ui-control gets the same context array and send it to ui-table I splittend it up to different nodes to make it easier to understand / debug - The tricky part is to scroll the table if you in… All depends on the type of data. The flow in the linked post is for growing data, like logging events. If you are updating data the `tabledata.push()` Is not enough. Then you need an object with an unique id for every row to keep your data in sync. --- _[View the full topic](https://discourse.nodered.org/t/newly-refreshed-dashboard-table-shows-stale-data-after-all-dashboards-closed-for-some-time/49730)._