# Perspective table, row selection, glitch on sort **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [March 27, 2026, 1:53pm UTC](https://forum.inductiveautomation.com/t/perspective-table-row-selection-glitch-on-sort/114725 "2026-03-27T13:53:13Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![Ryan\_Deardorff](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan_deardorff/32/63815_2.png) [@Ryan\_Deardorff](https://forum.inductiveautomation.com/u/Ryan_Deardorff)\ **Post date:** [March 27, 2026, 2:49pm UTC](https://forum.inductiveautomation.com/t/perspective-table-row-selection-glitch-on-sort/114725/4 "2026-03-27T14:49:08Z")
JavaScript? Not in Perspective… There have been other posts about the tricky nature of deselecting a table row: > [@Deselect and Un-Highlight Table Row](https://forum.inductiveautomation.com/t/deselect-and-un-highlight-table-row/79014/6): > > The most reliable way I've found to do this is to disable row selection, let that bounce over to the browser, which will then clear props.selection.data. A change event on props.selection.data can then re-enable row selection when it sees the new empty value. In general, properties that are set via user interaction in the browser, like selections, need to also be unset by the browser. Unsetting them directly via script (which runs in the gateway, not the browser) is unreliable. --- _[View the full topic](https://forum.inductiveautomation.com/t/perspective-table-row-selection-glitch-on-sort/114725)._