How to make the nextmatch grid/row value to null when changing responsible?

[Ki_Setargilop]

Hi there,

My EGW version is 1.9.019.

I have an issue of having a previously selected responsible appeared in the newly selected responsible in the infolog nextmatch index.

At first I selected user A in the responsible select box in the nextmatch infolog index which returns 282 overdue todos. Afterwards, I selected user B which returns 41 overdues todos. When I scroll down the table, it appears that user A still exists in the filter of user B. My guess is that the previous value of the ajax scroll is still there. How can I set the grid scroll value to null, so that the previous value will not appear? I tried tracing the code but it is very advanced in my level of expertise.

Thanks.

Ki

[ngegw]

I believe your guess is correct. We get some speed gains by not fully
clearing the table, but this is a bug. I hope to get to it in the next
days, but these ones are tricky to track down.
Are there any blank lines or white space between the end of user B and the
remnants of user A?

Nathan

[Ki_Setargilop]

Hi Nathan,

No blank lines in between of users. I tried tracing the get_rows returned value of user B and it turns out correct. It is just the ajax scroll rows having problems. Thanks for touching base on it. Hope this issue will be resolve.

-Ki

[Ki_Setargilop]

Hi Nathan,

Do you have any updates on this issue?

Thanks.

-Ki

[ngegw]

I still was not able to get this to happen, although I have seen (and
fixed) this problem before.
Unfortunately, the nextmatch/datagrid is extremely complicated and this
specific problem will need to be reproduced to fix.

You can try turning up debug in phpgwapi/js/jsapi/egw_debug.js line 42,
which provides a bit of insight.
The process really starts in et2_dataview_controller.js line 132 update().
Also of interest is et2_dataview_view_grid.js line 840, _doInvalidate()
which is responsible for removing unneeded rows.

Nathan

[Ki_Setargilop]

Hi Nathan,

Please see the attached screenshot to see the actual rows when changing the responsible. As you noticed I switched to ed but after the 20th row, the next row is randy. What is missing in the grid for js?

[ngegw]

I don’t know, but your screenshot provides a little insight.
Unfortunately, since I can’t duplicate it on my machine, you’ll have to do
the digging. It sounds like you can reproduce this on demand, which is
good.
Using the developer tools (network tab) on your browser, check the request
and see how many rows are sent back as data when you change the filter, and
if it matches the number of rows expected (you cropped out the row count in
your screenshot).

Nathan

[Ki_Setargilop]

Thanks.