# Power Table Row Freezing

**URL:** <https://forum.inductiveautomation.com/t/power-table-row-freezing/73340>\
**Category:** Ignition\
**Tags:** vision, ignition80\
**Created:** [May 5, 2023, 7:14pm UTC](https://forum.inductiveautomation.com/t/power-table-row-freezing/73340 "2023-05-05T19:14:25Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\
**Post date:** [May 7, 2023, 10:34am UTC](https://forum.inductiveautomation.com/t/power-table-row-freezing/73340/2 "2023-05-07T10:34:53Z")

</div>

I can think of multiple approaches that would work, but my inclination here would be to filter those two rows out of the dataset and overlay them in a separate table. If you are going to allow things like column resizing and reordering, then you will need [correlate the column model information](https://forum.inductiveautomation.com/t/8-0-vision-client-power-table-saving-column-order-sizing/31793/3) between the two tables to make it look seamless.

---

_[View the full topic](https://forum.inductiveautomation.com/t/power-table-row-freezing/73340)._