Table Binding: Cell Update - Dataset rows gets re-arranged

Ignition
1

The dataset rows get re-arranged when you add new columns to the table and then use the Table Customizer to adjust the columns:

(1) Add a table to your window
(2) Add a custom property to the table (name: editTable, type: boolean) (Click OK)
(3) Click the Data property (to add columns and rows)
(4) Add a column (name: Name, type: string)
(5) Add a column (name: Over18, type: integer)
(6) Add a column (name: Over50, type: integer) (Click OK)
(7) Open Table Customizer
(8) Click Boolean? for Over18 and Over50 (Click OK)
(9) Click Column Attributes Data Binding
(10) Choose Binding Type: Cell Update
(11) Select “editable” for Over18 (in the Dataset table)
(12) Click “Add” (green plus) for Cell Bindings
(13) Change Value to “{Root Container.Table.editTable}”
(14) Select “editable” for Over18 (in the Dataset table)
(15) Click “Add” (green plus) for Cell Bindings
(16) Change Value to “{Root Container.Table.editTable}” (Click OK)
(17) Click the Data property (to add columns and rows)
(18) Add a column (name: Over60, type: integer)
(19) Add a column (name: Over70, type: integer)
(20) Add a column (name: Over80, type: integer) (Click OK)
(21) Open Table Customizer
(22) Click Boolean? for Over60, Over70, Over80 (Click OK)
(23) Click Column Attributes Data Binding

In most cases, you will notice the names of the columns has been sufficiently rearranged that it makes your original cell bindings wrong and you have to go through and update all if not most of your row numbers. We didn’t even try to add columns at the beginning of the table.

To be sure, I was testing this in Ignition 7.5.6 but I have confirmed it still occurs in Ignition 7.5.11

2

There is a little hint at the top of the screen in the Cell Update binding window. It says that you can use a name/value pair instead of a row index.

3

Based on the title of this post it may be found while searching for a similar problem. I had a similar problem with data rows moving after an edit with a table that was bound to a query. The issue seemed to be the some edits changed that order that the data was retrieved by the query which made the rows move around in the table. I added and “ORDER BY” to my query and it stopped.