When you have a Grid with data and you filter on one of the values, that goes for more than one page, and you navigate to the next page, if you on the second page, try to filter for a value that has only one page, you get no results. If you move back to page 1, and then filters again, everything is back to normal.
Also spotted an issue when using -serversideprocessing it breaks pagination (numbered pages still show, but clicking them, while the number changes to indicate it’s been clicked, the data remains the same as if i were on the same page. as soon as -serversideprocessing is removed it functions correctly again).
Yeah, unless my understanding is wrong.
I basically have a ud grid, inside the endpoint i use the IIS app pool identity account to run an invoke-sqlcmd2 to pull data into a variable, run a for loop on that, and for each object, i transform the data with a few extra bits (a ud button in one of the rows which launches a modal) and so on.
I did notice that in the ud documentation for -serversideprocessing it says ‘This disables client-side filtering, sort and paging.’ Maybe it’s my understanding or usage that is just wrong in this case