# Manually adding items to props.selection.data on Table is being overwritten on first write **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [August 21, 2023, 11:11am UTC](https://forum.inductiveautomation.com/t/manually-adding-items-to-props-selection-data-on-table-is-being-overwritten-on-first-write/78147 "2023-08-21T11:11:42Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [August 21, 2023, 12:19pm UTC](https://forum.inductiveautomation.com/t/manually-adding-items-to-props-selection-data-on-table-is-being-overwritten-on-first-write/78147/2 "2023-08-21T12:19:29Z")
It's probably not going to work for you. There is some good explanation here: > [@Select all rows in a perspectives table](https://forum.inductiveautomation.com/t/select-all-rows-in-a-perspectives-table/77475/6): > > Unfortunately, Table.props.selection.data is read-only, and writing data to that property will not modify the state or appearance of the Table. The primary reason for this is that there is no guarantee of uniqueness in Table data. Imagine you had a Table with a single column "x" (just to keep the example simple), and it only had three rows: x ----- 1 2 1 Suppose now that you wrote the row data for the 2th (3rd) row with the expectation that the 2th row would display as selected. Well.… --- _[View the full topic](https://forum.inductiveautomation.com/t/manually-adding-items-to-props-selection-data-on-table-is-being-overwritten-on-first-write/78147)._