Hi Shivani,

Please suggest if you're using server side paging or client-side.

I believe this won't be possible with server side pagination, unless you manage a separate logic to maintain a list ofrecords that were selected in previous pages.

If it's client-side paging, then you can just keep a track of selected items by filtering records using the boolean variable that controls the row selection.

Regards to which items not being downloaded, it is purely on the logic on how you consider which rows are selected. Once you fix your selected items problem in pagination, this will be automatically resolved since you'll have which items are selected by user, so only consider all those items when downloading anything from the grid.

@Shivani Rajoriya you can add a boolean variable in your data structure to store the IsSelected value additional to the feature available in the grid for fetching selected rows.

When a selection happens on the UI for any record (or multiple records), set the value of this IsSelected variable to True, this way you won't lose the values of row selections after you turn the pages away. The current dataset on the screen will hold the value of that variable.

So whenever the user wants to export the records, you will have your own set of values taken from IsSelected variable to filter only the selected rows, and send it for exporting.