There are a lot of posts (and confusion) surrounding refreshing grids and things may be changing “under the hood” as “Kinetic” has evolved over time.
Below is a good example of such a post that may be helpful:
I think the uncertainty is based on how the grid is being populated.
- The grid could be populated by the grid’s Provider Model calling a BAQ. In this case, I would first attempt to use a Grid-Refresh event action. You need to make sure your grid has an ID, and then call out that gridID in the grid-refresh action.
I’ve also seen posts where users have noted that refreshing the grid doesn’t necessarily force the grid to rerun the BAQ. They’ve gotten around this by using a property-set to set the grid’s Invalidated property to “true” which then triggers the Provider Model to call the BAQ.
- The grid could be populated by a bound dataview which is set in the Grid Model properties. In this case, I would first attempt the Kinetic-BAQ event action to refresh the dataview, the grid should pick up those changes.
~*~
The problem, I think, may come from having a “mixed” setup. A grid that is set up to use the Provider Model as the primary “source of truth”… the grid is tied to a dataview… then you use an erp-BAQ event which updates the dataview… but the grid may be still treating the Provider Model as the source of truth and isn’t reapplying your View Options.
I would try swapping out your erp-baq (kinetic-baq) event action with a grid-refresh action and see if (A) your grid refreshes… and (B) your View Options are then honored after the refresh.