Hi Guys,
A quick one: I understand the concept of grabbing the grid state via "grid.getOptions", then persisting this, and then applying it again via "grid.setOptions" on form refresh to keep the users' sort/filter/column options, etc between sessions. There are posts and help for this already.
My question is this:
- In our situation, we do the above persistence, and store the options string somewhere (e.g. database).
- However, we may well change the set of columns that the grid needs to display when we do an application version update. It's likely that we would remove, or add columns for example.
- So, if we have try to apply an options set to the grid that has some columns missing or added since the "save" of the options... what happens?
Does it:
- Robustly (silently ignore) options we are trying to apply for columns that no longer exist in the grid?
- Robustly (apply a default) for columns that do not have any options being applied? (e.g. newly added columns).
- Throw errors, but still render?
- Fail to render with errors?
- Something else?
cheers
Nick