# How to clear selection from Perspective Alarm Status Table

**URL:** <https://forum.inductiveautomation.com/t/how-to-clear-selection-from-perspective-alarm-status-table/101101>\
**Category:** Ignition\
**Tags:** perspective, vision\
**Created:** [January 20, 2025, 12:26pm UTC](https://forum.inductiveautomation.com/t/how-to-clear-selection-from-perspective-alarm-status-table/101101 "2025-01-20T12:26:30Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [January 20, 2025, 1:20pm UTC](https://forum.inductiveautomation.com/t/how-to-clear-selection-from-perspective-alarm-status-table/101101/4 "2025-01-20T13:20:27Z")

</div>

A hack you could try would be to set the selection mode to "none", then set it back after a delay.

A similar trick works for the regular table component:

> [@Row selected problem in Perspective table](https://forum.inductiveautomation.com/t/row-selected-problem-in-perspective-table/100580/2):
>
> The trick is to set enableRowSelection to False, and have a change script on selectedRow looking for None, and then changing enableRowSelection back to True. The code must not set enableRowSelection to False when selectedRow is already None. Basically, row selection can only be performed reliably by the client browser. When you disable row selection, that state gets sent to the browser, and it clears the selection. When you see that change back in the gateway, you can re-enable row selection…

---

_[View the full topic](https://forum.inductiveautomation.com/t/how-to-clear-selection-from-perspective-alarm-status-table/101101)._