# BUG: Table fields not ediable after setting data

**URL:** <https://forum.inductiveautomation.com/t/bug-table-fields-not-ediable-after-setting-data/35979>\
**Category:** Ignition\
**Created:** [June 24, 2020, 1:38pm UTC](https://forum.inductiveautomation.com/t/bug-table-fields-not-ediable-after-setting-data/35979 "2020-06-24T13:38:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sanderd17](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sanderd17/32/8735_2.png) [@Sanderd17](https://forum.inductiveautomation.com/u/Sanderd17)\
**Post date:** [June 24, 2020, 1:38pm UTC](https://forum.inductiveautomation.com/t/bug-table-fields-not-ediable-after-setting-data/35979/1 "2020-06-24T13:38:59Z")

</div>

This one took a long time to figure out, but I bumped into a nasty problem.

I made a table with some data, and set the columns to be editable.  
At this point, I was able to edit the data, and the cellEdited function was executed.

But when I assigned a new dataset to the table data (`table.data = system.dataset.toDataSet([...], [...])`), I was no longer able to edit the data.  
When checking it in the designer, the `editable` checkmarks on the table were unchecked, but they were still checked in the column attributes dataset.

Is this a known bug? And is there a solution for it?

Edit: I’m using Vision 8.0.13 at the moment

---

<div class="post-metadata">

**Author:** ![code\_skin](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@code\_skin](https://forum.inductiveautomation.com/u/code_skin)\
**Post date:** [June 24, 2020, 1:48pm UTC](https://forum.inductiveautomation.com/t/bug-table-fields-not-ediable-after-setting-data/35979/2 "2020-06-24T13:48:33Z")

</div>

When you assign a new dataset and the column names are different, I’d expect the editable properties to reset. Is this the case for you?

I’ve experienced this with Vision when I’m “clearing” out a dataset and the way I preserve column settings is:

```auto
table.data = system.dataset.toDataset(system.dataset.getColumnHeaders(table.data), [])

```

---

<div class="post-metadata">

**Author:** ![Sanderd17](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sanderd17/32/8735_2.png) [@Sanderd17](https://forum.inductiveautomation.com/u/Sanderd17)\
**Post date:** [June 24, 2020, 2:29pm UTC](https://forum.inductiveautomation.com/t/bug-table-fields-not-ediable-after-setting-data/35979/3 "2020-06-24T14:29:58Z")

</div>

No, the column names are the same.

---

<div class="post-metadata">

**Author:** ![code\_skin](https://avatars.discourse-cdn.com/v4/letter/c/43a26b/32.png) [@code\_skin](https://forum.inductiveautomation.com/u/code_skin)\
**Post date:** [June 24, 2020, 2:39pm UTC](https://forum.inductiveautomation.com/t/bug-table-fields-not-ediable-after-setting-data/35979/4 "2020-06-24T14:39:57Z")

</div>

I can’t reproduce this in 8.0.14. Are you able to update to see if that resolves your issue?

Edit: demo below

[https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/e/5e4e515b4eddbf221d98afb40ef40942e49b045d.mp4](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/e/5e4e515b4eddbf221d98afb40ef40942e49b045d.mp4)

---

<div class="post-metadata">

**Author:** ![Sanderd17](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sanderd17/32/8735_2.png) [@Sanderd17](https://forum.inductiveautomation.com/u/Sanderd17)\
**Post date:** [June 24, 2020, 2:51pm UTC](https://forum.inductiveautomation.com/t/bug-table-fields-not-ediable-after-setting-data/35979/5 "2020-06-24T14:51:05Z")

</div>

Thanks a lot. It looks like this was the correct solution after all. There must have been a small difference between the headers I gave and the headers that were already on the table. But by taking the existing headers it does work again.

> [@code\_skin](#):
>
> system.dataset.getColumnHeaders(table.data)