Giving a dashboard some memory

I’ve been struggling with working through a problem. I’ve been attempting to use the row-find and row-current-set row actions to remember the row index of a grid before a user clicks refresh all so after the refresh the row pointer on the grid is set back to the row the user was at before they refreshed. Am I on a fools errand, or is this just another undocumented quirk?

It’s a multi grid dashboard and the premise of the solution was to have one refresh button that refreshed all grids, and remembering the current row of the “Parent” grid would cascade down and keep everything in synch.

Using the row-find and row-current-set I can see the index getting set in the debugger, but it does not update the grid. I’ve seen a few threads on using the row-current-set using the rowindex, or even using js to set the index for example using #(trans.dataView(‘’).row)# as the expression. as well as references to using the viewRow value… nothing has got it to work.

The only other thought… is that it is not working because of some incapability of the dashboard to work because it was uplifted from classic. (I know, I am looking into an issue, we really know the answer I think, but want to eliminate).

Here’s a snip of the debugger.

Any suggestions before I lose the rest of what little hair I have left. :slight_smile:

Thanks

I did find PRB PRB0276273, but the steps to replicate sound like it working, but it appears substition of the rowindex with a varible may be the issue.

1 Like

I think I remember trying this and the issue is that the parent/child relationships dont refresh the child grids when you row-current set on the parent. The logic you are using works for the parent grid but none of the child grids will update their filter per the new parent grid’s selection.

If I recall, what I did was something like leave the parent child relationships in place which work if the user clicks on the grid manually. And then when I did my refresh event, I row-current-set the parent grid then manually triggered a refresh on all the child grids after row-current set on the parent, something like that. Then I think I row-find, row-current-set on the children too.

T

Thanks for your response @GabeFranco
At this point I am only just wanting to update the parent. Perhaps it’s the fact that the dashboard was created as a classic dashboard and uplifted… IDK… and was going to be my next course of action to take a simple grid with the same baq and see if it works. Definately been a frustrating one.