GridModel -> BAQ Server Side Paging

I am struggling hard to make a grid bound toa BAQ be pageable (server side) / scroll. I"ve chcked all the right boxes (me thinks)

But it still either blows up, does’nt run, or doesn’t page.

Does anyone have an example of a working App Studio Grid Model that does server side paging for a large and complex baq?

Commenting not with the answer but because I’d like to know, too.

For almost everything to do with grids and BAQs I’ve ended up falling back on manual events, because even when I get it working using the grid properties something seems to change in the next update and it breaks.

Something has changed since I last tried this in 2024.2. I wasn’t able to get it to work either.

You used to be able to just check the “Server Paging” checkbox in the provider model. If I do that now, the BAQ will not run. If I also check “Auto Refresh grid On Load”, ExecuteBaq is run twice. First with no page size/ page num, second with it.

Yeha, its a mess. I’ve tired several different combinations with little to no success.

I created a support case with it fresh on my mind. Let’s see what they say

Return Of The Jedi Episode 6 GIF

I wonder if this is the fix

KNTC-30010-1221003 This hotfix addresses these issues: KNTC-29974 Honor provider model config for server paging in baq grids, KNTC-29890 group info should stay consistent when panel card collapses/expands, KNTC-29408 Reverted changes for enabling count for non-numeric columns
KNTC-29979-1221003 This hotfix addresses a scrolling issue in BAQ grid display

Good catch @hkeric.wci! hotfix KNTC-30010-1221003 worked for me with “Server Paging” and “Auto Refresh grid On Load” checked. Although this hotfix is for 2026.100, I gave it a try in my 2025.2 Test environment.
I wouldn’t trust using this in production, but I will ask if they can apply this fix in 2025.2 as well.

Nice! Look forward to seeing if grouping/filtering/paging all work together as they should. Hopefully they dropped the client-side sql select for aggregates and are doing it more kendo-style.

I avoid using the provider model entirely in the last couple of month and everything is much more stable and robust since then. Those dashboards went through the 2026.100 update with no issues. The early one I did with provider model and wizard on the other hand…

Problme is without the provider model you lose tha ability to page results. At least in a reliable/simple way.