7 Answers, 1 is accepted
I can assume that with LoadSettings means that the Grid will be loaded with a JSON formatted setting coming from the server for example.
If this is the case, then the multi property is set via columns[i].filterable.multi = true.
A similar format can be observed in our jQuery demo:
If my assumption is not correct, please provide more details about the scenario and I will gladly assist.
No, I am using the Razor function, wee below. "Model.Columns" is a list of objects that descend from "GridColumnSettings". GridColumnSettings does not contain a property called Filterable. The only thing filter related it contains is called "FilterUIRole", which is an enum. It seems the value I want to set doesn't even exist.
Thank you for the clarification.
Indeed, not all of the properties are available when using the LoadSettings option.
I logged an issue in our GitHub repository for adding all of the other options.
In the meantime, I can suggest using the other approach for setting the column options:
Apologies for the inconvenience this may have caused you.
Can I get some more information about that "issue", i.e. priority, status, etc?
I need to use the LoadSettings method because we have a re-usable grid control that we built using the kendo grid.The alternative is not doable.
You can monitor the status of the issue in our feedback portal in the following link. Furthermore, other users can also vote for the feature in order to increase its priority.
I have landed here after stumbling on the same issue. It seems the LoadSettings way does not support all of the features in the column configurator.
In my case we had a grid with a variable number of columns (generated dynamically) and that was why using the "normal" way wasn't an option.
Here is how I got around it:-
1. Extended the GridColumnSettings class to accommodate the extra features I wanted.
2. Instead of passing the List<GridColumnSettings> to the .LoadSettings method, iterated through the new list and used the "normal" way to configure the columns. Something like this:
Thank you for sharing your implementation with the community. This can help someone looking for similar functionality.
Our thoughts here at Progress are with those affected by the outbreak.