Different grid refresh-after-update behavior if using Search Part

[christappan]

This started out as one post and then I tested some more things and my question evolved. So here's where we'll start.

Example: Take a grid where the query has a WHERE Order_Processed = 'No'. The user opens the record detail view, marks the control to make Order_Processed = 'Yes'. The user hits save and the the detail view closes. Here are the options for Detail View Properties "Row refresh method after edits":

1) Single row: quick, but the record remains in the grid even though Order_Processed now equals 'Yes'. If the user tries to re-open this row, they get an error "Fatal error running a5_ajax_grid(): Result set row requested not found while getting result set data column..."

2) Minimal and Auto-Select seem to have the same behavior as Single Row in this scenario.

3) Full Refresh: the row won't be displayed any longer, which is good, but the grid has to do a full refresh. With a couple of joins and a few parameters in the WHERE statement, this is overkill on the server to have to do the entire query every time a user edits a record.

I'll say too that I have one grid that is editable and just displays one record at a time, which works fine. But there are other needs where users need to see these records because they are time-sensitive but they also need to be able to see all the records in the grid if they need to look for certain record types.

After further testing, I found that if I take the WHERE Order_Processed = 'Yes' out of the query and put a control in the Search Part to search only on records where Order_Processed = 'Yes', then the Single row refresh method leaves the record in the grid but there's not an error if the user tries to re-open the record.

Is this a bug, just the nature of the beast, and/or does anyone have an idea for what I'd really like to see, which is that the single row would remove itself from the queue without the grid having to do a full query?

Any and all thoughts are welcomed.

[Davidk]

Re: Different grid refresh-after-update behavior if using Search Part

Hey Chris,

I understand what you mean, but I have to go with "the nature of the beast". It's a database... you have to go after the data after a change... it's not just local data so there's no choice but to go after your records again. I don't know if it's possible in your app, but other users may have changed other records which are no longer available to your grid and so you need to include those edits as well.

You simply want to see that row in the grid disappear... but without going after the data again how do you know what else has changed other than your row. On my simple grid the row does just disappear... and quickly, but with your more complicated query I don't think there's much you can do.

This is probably a silly suggestion, but... try setting the Detail row update to Minimal... and... in the Grid's Client-Side Events, afterDetailViewSubmit... put {Grid.Object}.refresh();

It's still doing a refresh and it's probably exactly the same as Full Page, but see if there's any difference for you.

[christappan]

Re: Different grid refresh-after-update behavior if using Search Part

Thanks for replying David.

I've tried the {grid.object}.refresh() method in another component--like you said, it's still running the full query. I understand what you say about it having to go after the data again, and I guess I was hopeful for some kind of opposite of inserting a record--you can do that without doing a full refresh and the row shows up in the grid, albeit in the wrong place based on the ORDER BY. If an edited record could check only itself against the grid query and the grid could keep or eliminate just that row... I guess that's just the stuff of dreams...

Thanks anyway.

[Davidk]

Re: Different grid refresh-after-update behavior if using Search Part

Not completely sure about this, but, since the Grid is very "data" aware, you could use a Dialog to get the effect you want. You'd have to look after all the bits yourself, but you could control it's behaviour a bit more.

[agillbb]

Re: Different grid refresh-after-update behavior if using Search Part

I think the full refresh is the most robust way to deal with this. Chances are your users won't be deleting too often, and will be willing to wait a second or two. You could also work on speeding up the query itself (DB indexes).