All of that was set up the way it was intended. He was just suffering from the elusive spelling error. 
ā¦ and what even is the āprovider modelā???
I mean I have a vague idea from the name but would love a better handle on exactly how grids are engineered.
I highly doubt that. Why would the view filters and together like that ?
The model thatā¦
ā¦ wait for itā¦
ā¦ keep waitingā¦
Provides the data!
Itās used when youāre not populating the DataView from an event. The provider model is supposed to use REST or BAQID to populate the grid as itās created.
That was a glitch and Iām unsure how that happened, but the way he has it configured now it as intended.
Yesā¦ but the original, perhaps naive, setup should have worked too? Without arcane knoweldge of what fires when under the hood (which Iām still only guessing at), the accumulation of the client filters was most surpising. And sounds like only happens on BAQ derived data?
Iāve been moderately popcorning this, Iāll have to go back and re-read it later.
Honestly, this whole bit seems sus.
Iāll see if I can replicate it tomorrow.
1 Like
Yes, Iām inclined to think itās a bug, unless there was some unseen setup issue overlooked.
I meanāI feel like it should. Maybe that was all due to your spelling error? Lol!
I know Iāve used the view options before without setting the BAQ info up there, but if anything goes awry, I tend to default back to the way we just set it up.
Itās all black magic anyways.
Real GIF of me learning App Studio.
1 Like
Pretty sure I had it right or my client side filters wouldnt have worked at all. Next question is how the hell did I then get it wrong moving it to the BAQ. Might be because its 1.46 am here now 
Goodnight folks!
(I had a question about how @hmwillett got funky colors in the custom app, css maybe? but thatās for another day, another thread)
You donāt have that?