I am working on a custom grid related to an updateable BAQ, which has an add new function which also automatically saves and refreshes the data. The data view behaves exactly as I would expect, but the UI grid sometimes displays whatever row is selected instead of the newly added data.
If I click anywhere else in the page it refreshes and shows the correct data, but no matter what I do in the event it doesn’t display properly. Using a Grid Refresh event node, setting the focus to a different control or data view, setting the property “invalidated” of the effected grid to true, none of them seem to effect the final row.
Has anyone run into this before? I’ve replicated it in both 2025.2.5 and 2025.1.11.
1 Like
So I have run into two different issues, not sure if either of these is what you are talking about exactly. The first issue is that the user selects a row other than the first row in the grid, then does something that triggers the grid to refresh. Now the first row of the grid is selected (with the little arrow) but whichever row they had clicked on before is still highlighted. This is super confusing when another grid is subscribed and its not clear which row its feeding from. I have been meaning to see if I can force the highlighting to match the row selection but haven’t gotten around to it.
Second issue is an event that triggers data to refresh in the grid, but there is only one record in the grid. The data does refresh (if I look in the dataview I can see the new data there) but the grid doesn’t show me the new data until I somehow navigate away from the grid. This makes it seem like the update has not occurred when it has.
I think the second one might be what you are talking about? Or at least related?
I haven’t tried to report these issues to support because I know the time investment to get them to reproduce is going to be severe (starting with, click to create a new layer 
) have you opened a case yet?
2 Likes
Neither quite match - if I put in a select final row node after the save it selects the final row properly so both the highlight and the selection are on the same row.
And it seems to occur no matter how many rows I have, but they might be related.
I have opened a ticket with Epiccare, but they said their only option would be to reproduce and send to development and that doesn’t seem likely to provide a quick resolution.
