Server-side data processing improves the widget's performance on large datasets. When the server does not implement particular operations (and/or the corresponding remoteOperations fields are false) they are executed on the client. Note that the widget may send queries to the server while executing a client-side operation.
The following table lists the possible remoteOperations configurations and the operations the server should implement. The server should also implement additional operations depending on the used widget functionality.
|Setting||Required server-side operations||Additional server-side operations|
||all operations except group paging||-|
||all operations including group paging||-|
||paging||filtering1, sorting1, summary calculation1|
(with grouping used in the widget)
|paging, filtering, sorting||grouping3, summary calculation1|
||grouping, filtering||sorting1, summary calculation1|
||summary calculation||filtering1, sorting2, grouping2|
The following restrictions apply to widget functionality when operations are remote:
Custom summary calculation is not supported.
The calculateFilterExpression option does not apply if it returns a function or a filter expression that contains functions.
Specifies whether or not filtering must be performed on the server side.
Specifies whether or not grouping must be performed on the server side.
Remote group paging allows you to load groups from a remote source in portions. This feature speeds up grouping because the DataGrid transmits less data. However, requests are more frequent because the DataGrid sends several requests each time a user expands a group or sorts/filters data.
Remote group paging has the following specificities:
Specifies whether or not paging must be performed on the server side.
Specifies whether or not sorting must be performed on the server side.
Specifies whether or not summaries summaries are calculated on the server-side.