# Select all rows in a perspectives table

**URL:** <https://forum.inductiveautomation.com/t/select-all-rows-in-a-perspectives-table/77475>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [August 4, 2023, 6:06pm UTC](https://forum.inductiveautomation.com/t/select-all-rows-in-a-perspectives-table/77475 "2023-08-04T18:06:41Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [August 18, 2023, 3:08pm UTC](https://forum.inductiveautomation.com/t/select-all-rows-in-a-perspectives-table/77475/6 "2023-08-18T15:08:57Z")

</div>

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:

```auto
  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... `{"x": 1}` actually defines the underlying data of two rows, so which should be selected?

There's no good work around, because there is no current way for the Table to dynamically or systematically have selection applied to it.

A _bad_ workaround is to add a new column to the Table (and your data) as the 0th column, render it as a boolean field (checkbox or toggle), and use some external component (perhaps a Button) to set the underlying value of the data to have all rows selected. You would also then need to supply your OWN style to each row to designate the row as selected.

---

_[View the full topic](https://forum.inductiveautomation.com/t/select-all-rows-in-a-perspectives-table/77475)._