# Table setSelectedColumn

**URL:** <https://forum.inductiveautomation.com/t/table-setselectedcolumn/7212>\
**Category:** Ignition\
**Created:** [September 6, 2013, 6:52pm UTC](https://forum.inductiveautomation.com/t/table-setselectedcolumn/7212 "2013-09-06T18:52:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![weertske](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/weertske/32/3353_2.png) [@weertske](https://forum.inductiveautomation.com/u/weertske)\
**Post date:** [September 6, 2013, 6:52pm UTC](https://forum.inductiveautomation.com/t/table-setselectedcolumn/7212/1 "2013-09-06T18:52:01Z")

</div>

The table setSelectedColumn script exhibits unusual behavior. If I have a “cell edited” script and within that script have the line "setSelectedColumn(7) and then edit column 1, when I press “enter” the next column selected is, correctly, column 7. Same for columns 2-6. However, if I am editing column 7 and press enter, the next column chosen is not 7 but rather 8 in violation of the setSelectedColumn(7) command.

This behavior is causing me a problem in a “cell edited” event where I am monitoring the data being entered to make sure it is in range. If it isn’t in range, I pop up a message box informing the operator of the error and then have the script select the column they just entered so they can try again. I can’t get it to happen. I can select any other column but not the one they just edited.

Version 7.5.8

---

<div class="post-metadata">

**Author:** ![Robert.McKenzie](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/robert.mckenzie/32/4134_2.png) [@Robert.McKenzie](https://forum.inductiveautomation.com/u/Robert.McKenzie)\
**Post date:** [December 24, 2013, 4:43pm UTC](https://forum.inductiveautomation.com/t/table-setselectedcolumn/7212/2 "2013-12-24T16:43:33Z")

</div>

It looks like this is working for me in version 7.6.4, have you updated to the latest 7.5? If so are you still seeing this issue?
