We are receiving the message "Can't select that many records at once". This happens when the user selects a record, then scrolls farther than the page size and shift-selects the next record from the new batch fetched where the scrolling landed. I understand the reason for the message is that the user has selected a range of records within which not all records have been loaded into the Grid/result set
We are using grid paging and don't want to always load all records at once, to ensure the user has them available to select.
We are looking for a way to prevent this message from being triggered by ensuring all records in the users selected range are fetched at the time of shift-selection.
Is there a way to intercept the message from being triggered? ( and subsequently fetch to ensure the records are there before the selection action continues/completes)
We are using grid paging and don't want to always load all records at once, to ensure the user has them available to select.
We are looking for a way to prevent this message from being triggered by ensuring all records in the users selected range are fetched at the time of shift-selection.
Is there a way to intercept the message from being triggered? ( and subsequently fetch to ensure the records are there before the selection action continues/completes)