I have a perspective table with a data binding that queries a database. The column field names correspond to column names in the database table. If I create a table column with that field name and set it to invisible, the column is still visible. Furthermore, if I give that column a new header title and set the column to visible, the column is properly renamed, and therefore I know the field name matches the field name of the data from the query.
Here the column quantityScheduled is set to not be visible but is still visible.
Here the column quantitySchneduled is set to visible. You can see the column is renamed because the header title is set, so it's not a problem with the field name setting.
This problem extends to all columns for data that is retrieved from the query that are set to invisible
The fact that it shows up to the left of Status when set to visible, but to the right when not seems like a clue. Are you sure the field name is an exact match? We can't see the full field name in that first screenshot because the column isn't wide enough...
Have you tried just leaving that one out of props.columns ?
1 Like
When the column is set to be not visible, the order is as it appears in the query result which is alphabetical (roughly). When the column is set to visible, it moves to the order as defined in props.column.
I am sure it is an exact match. I have copied and pasted it from the source, and the fact that the column is renamed and moved when set to visible proves that it is an exact match.
Yes I have tried that, and the column is still present
Check all of your props.columns[x].field settings.
If in doubt, delete all but the first, see if you get just that one column displayed. Then add back one at a time.
If a column is specified but not found, the table will automatically display the next column from the dataset without config, and fill the space where it would go.
