# Capture snapshot data for UI table

**URL:** <https://discourse.nodered.org/t/capture-snapshot-data-for-ui-table/57599>\
**Category:** General\
**Created:** [1 February 2022 15:41 UTC](https://discourse.nodered.org/t/capture-snapshot-data-for-ui-table/57599 "2022-02-01T15:41:56Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**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:** [1 February 2022 16:51 UTC](https://discourse.nodered.org/t/capture-snapshot-data-for-ui-table/57599/2 "2022-02-01T16:51:59Z")

</div>

Perhaps you can get some insights how the row index works in this post and the complete thread

> [@Stop ui-table from auto-numbering column](https://discourse.nodered.org/t/stop-ui-table-from-auto-numbering-column/57159/6):
>
> Hi, As I see your table the data comes from measuring devices which should have any kind of unique id (I use the mqtt topic for all data comming in from mqtt devices or the serial number of others. Send this id with all your data {id:"device001",value:123.12} So if you send a new value later {id:"device001",value:999.99} using the updateOrAddData function call the value will be updated. Best practice is to send only the changed values to keep the traffic load low and be able to use something l…

I’m traveling so I can’t look into your flow soon. So you might provide a incremental index in your case (a timestamp for example) and declare this column as index. You can even hide this column if it isn’t useful to display

---

_[View the full topic](https://discourse.nodered.org/t/capture-snapshot-data-for-ui-table/57599)._