Submitted by WayneK on 2022/07/18 11:19

I know I posted this a long time ago but will dredge it up again because I find that the limitations in loading column sets really reduces their usefulness.

When you load a column set:

1) It does not preserve column arrangement (the order is preserved but all columns are loaded to the right of the item column)

2) It does not preserve column groups (groups are disbanded)

3) It does not preserve hidden columns (all columns are loaded)

The above means you have to do considerable manual re-arranging to correctly reproduce the column arrangement of the source.

When creating a new grid, you can get around this by using "Save as" to create a new grid (followed by deleting items to order a new blank grid with the correct column arrangement).

Where it really limits you, though, is in being able to switch between column sets in a given grid.  This would be a nice way to avoid creating new grids but it isn't practical because it requires too much manual re-arrangement every time a new set is loaded.

Wayne

Comments

Hi Wayne,

Indeed, the original concept of column sets was to be to switch between sets of columns while keeping some common ones (item and other locked columns. Then hidden columns were added, and then column grouping, etc. It is becoming difficult to manage the "fusion" between the grid native columns and the loaded column sets

What I'm now contemplating is that column sets could completely replace all columns. It would be much simpler to implement and conceptually easier for users too.

Feedback anyone ?

Sounds good to me, if I understand you correctly.  I've never tried retaining locked columns while loading another set.  I always replace all columns so presumably this would implement what I'm already doing.

Wayne

Suggestions