[soldham]

I think I got it worked out. For reasons not clear to me, the dashboard file ended up with a “.settings” node that seemed to include the misconfiguration that I’ve been trying to get rid of. The contents of that node in the dashboard file matched what I was seeing in the local storage in the browser developer tools window. I deleted the node from the file in a text editor and the problem went away. I don’t understand how those settings got baked into the dashboard file or why they only applied in non-edit mode or why I wasn’t able to correct them using the dashboard editor but I’m glad to have this resolved. If any other dashboard users have a similar experience maybe this thread will be of use to them. In case the KX developers care to investigate this further, I am including the notebook file with the errant “.settings” node here

[soldham]

Hi David. Thanks for sticking with me on this. I usually manage the order and visibility of datagrid columns in the ‘Columns’ section of the datagrid control panel in edit mode but I did as you suggested, using Configuration, and it seemed to fix my problem until I reloaded the page, at which time the undesirable ordering re-appeared.  I have found that the undesirable ordering is encoded in a piece of browser local storage which you can see here.

In edit mode the local storage is empty so I suspect that the difference comes down to this. I have tried using ‘Reset View State’ in non-edit mode, and I have tried deleting the local storage in developer tools but it always comes back.

 

[soldham]

Hi David,

Thanks for the suggestion about resetting the view state in no-edit mode. I did that but the difference between the two modes persists.  Unfortunately, I am not a KX Control user so I don’t think your second suggestion will help in this case. Any other ideas?