Hi David,
A friendly reminder and ask for input (in case the item is still relevant). We will appreciate your comments and input on the item in the coming month. Alternatively, let us know if the case is resolved and we can close it. 

Kind Regards, Maria VeledinovaPM at Progress Telerik

Hello, David,

Thank you for the additional details!

I tried reproducing both of the problems, however I was unable to, perhaps there's a difference between our configurations.

Problem 1:

https://dojo.telerik.com/@gdenchev/OteDajUq 

Problem 2:

https://dojo.telerik.com/@gdenchev/ezizAsUL 

In the first Dojo, one of the columns has its field changed before the options are reapplied, however nothing seems to break. In the second Dojo the toolbar is changed before the options are set back but again nothing seems to break.

I also wanted to take a moment and go back the the initial post and more precisely the fourth point.

Only apply/change the filters, sorts and groupbys via a setOptions() on the grid that is passed down as opposed to a set of the entire object.

The setOptions method does not expect the entire object generated by getOptions to be passed down. You can change any of the grid properties one by one as well.

// Change the filterable configuration
grid.setOptions({
    filterable: false
});

// Change the pageable configuration and the Grid columns.
grid.setOptions({
    pageable: true,
    columns: [/*...columns array*/]
});

You may also delete parts of the object created by getOptions() and reapply only some of them. As far as filters, sorts, groups go, these are applied to the dataSource itself, not the Grid. The setOptions method doesn't have relation to these settings, other than the fact that getOptions also saves the dataSource object(which could be excluded when you reapply the settings).

Would you mind updating the Dojos to reproduce the problems you were describing so I can forward them to the Dev team for a review?

Best Regards,
Georgi Denchev
Progress Telerik

Hello, David,

Thank you for all of the provided details!

However I am not quite sure what the exact Feature Request is?

Generally speaking there could be certain scenarios where using getOptions and setOptions directly may not be optimal or may not work altogether. In these situations it is best for the Developer to manually set particular configurations, as you have already done.

However these are project specific modifications and while they may work and help some people, they may also cause troubles for others(if they are implemented by default for everyone). That is why getOptions exposes all of the currently applied configurations which you can further modify and then set them back to the Grid via setOptions or some other method.

Could you please elaborate a bit more about the request that you have?

If you wish to share your solution with the rest of the community, we can create a Knowledge Base article which anyone can read.

Best Regards,
Georgi Denchev
Progress Telerik