# Adding a column before another: issue with bindings

**URL:** <https://forum.inductiveautomation.com/t/adding-a-column-before-another-issue-with-bindings/56364>\
**Category:** Ignition Early Access\
**Tags:** perspective\
**Created:** [February 21, 2022, 2:56pm UTC](https://forum.inductiveautomation.com/t/adding-a-column-before-another-issue-with-bindings/56364 "2022-02-21T14:56:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gdube](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/gdube/32/41701_2.png) [@gdube](https://forum.inductiveautomation.com/u/gdube)\
**Post date:** [February 21, 2022, 2:56pm UTC](https://forum.inductiveautomation.com/t/adding-a-column-before-another-issue-with-bindings/56364/1 "2022-02-21T14:56:50Z")

</div>

Hi guys,  
In a Perspective Table, I added a column to props.columns before an existing column, and the bindings on my existing column didn’t stay on it. Instead, they were now applied on the new column.

---

<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:** [February 21, 2022, 2:59pm UTC](https://forum.inductiveautomation.com/t/adding-a-column-before-another-issue-with-bindings/56364/2 "2022-02-21T14:59:11Z")

</div>

Known behavior. Bindings into arrays have fixed subscripts. Discussed ad-nauseum on this forum. I believe the last determination from IA was “not a bug, won’t fix”.

---

<div class="post-metadata">

**Author:** ![gdube](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/gdube/32/41701_2.png) [@gdube](https://forum.inductiveautomation.com/u/gdube)\
**Post date:** [February 21, 2022, 3:14pm UTC](https://forum.inductiveautomation.com/t/adding-a-column-before-another-issue-with-bindings/56364/3 "2022-02-21T15:14:45Z")

</div>

Well that’s bummer. Weird that they don’t consider it a viable scenario. I guess to keep bindings intact if you bind directly on props.columns?

Thanks anyway.

---

<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:** [February 21, 2022, 3:16pm UTC](https://forum.inductiveautomation.com/t/adding-a-column-before-another-issue-with-bindings/56364/4 "2022-02-21T15:16:34Z")

</div>

Yes, it is best to generate the entire array in the binding if you need what would otherwise be movable bindings.

---

<div class="post-metadata">

**Author:** ![victordcq](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@victordcq](https://forum.inductiveautomation.com/u/victordcq)\
**Post date:** [February 21, 2022, 3:24pm UTC](https://forum.inductiveautomation.com/t/adding-a-column-before-another-issue-with-bindings/56364/5 "2022-02-21T15:24:55Z")

</div>

Its simply not possible to do, json array’s are indexed my number.  
A program cant know if what ever is in it moves to a different index or not.  
That would require a structured object, which also has its downsides, which is why there is a combination of both in ignition.

It might be useful if igntion would give a warning when you bind something to an array though