App Studio Dashboard - Two Grids on Same Dataview/Different Filtering

So, in a Classic dashboard it’s easy to attach multiple grids to a single dataview and enter different filters on the grids.

This particular application I’m recreating in Kinetic marks an “unstaged” row in one grid and it magically teleports to the other “staged” grid (or the reverse), according to the grid filtering. I want Stage = false in the first grid and Stage = true in the second.

In Kinetic, I can attach a second grid to the dataview, but can’t seem to find the right place to place filters.

There is a Client Filter on the provider model, but that seems to work only on data load from the BAQ from the grid where the BAQ is attached, and it filters out all rows on the second grid where the dataview is set at the grid model level.

I could add another dataview, do a save on the changed grid, and then reload both dataviews, but that would be pretty dang slow on this dataset.

Any suggestions?

Thanks,

Joe

2 Likes

Are your grids using Provider Model? If so, you can do it in BAQ Options - Where List. That’s where I’ve done it for a few of our dashboards with multi-grids with same DV.

When I have the same DV attached to two grids, the filtering I do on one grid with Provider Model > Baq Options - Where List will carry over to the other grid– I’ll have two identical grids. The same DV and BAQ ID are used on both. I figured the Where List would apply only to that one grid but I guess not?

If I want two grids with different filtering on the same dataset, I’ve been making two separate DV’s, assigning each to their own grid and using their corresponding Where Lists’. View Options works great when I just want a single grid with different filtering on the same DV, but I’ve always had to make separate DV’s when I want multiple grids to have different filtering on the same dataset.

That’s odd, we have a few dashboards and the where lists weren’t combining before. I’ll have to go figure out which ones and test them. They were built in 2024.1 or .2 so maybe something in 2025?

Why not just create two different view options in the same grid?

1 Like

A little clarification.

The dataview has a calculated field on an updatable query, and it is always set to false upon data load.

On the classic dashboard, when you click the checkbox and mark it true, the filters take the row out of the top grid and place it in the bottom grid, where the user can update a field or run a custom action in the BAQ.

That’s easy to do on the classic dashboard, but I’ve not found a way to get that functionality.

Using filters on the provider model seems only to work on data load. I’ve not found a way to persuade the grids to recheck their filters when the value changes.

And I’ve tried more ways than I have time to enter here, but basically, I have an event that fires when the column changes. And from there I’ve tried rebinding, setting grid filters (the user filters at the top of the grid), yada and yada.

I’ve used two dataviews of the same BAQ source, and have made copies of the dataview and then filtered those for display purposes, but this updatable thing is a different animal.

Basically, they want it to work something like invoice entry where you click on shipped orders and it puts the selections in a box for more processing. But it’s still in the original dataview and you can uncheck the box and send it back to the main grid.

It could be more trouble than it’s worth. :-/

Thanks for your responses.

Joe

1 Like