Dynamically set a filter after Add

Jaymer

Assume a list of Customers are showing in a Grid.
I have a NEW Customer button.
After saving I want to display that new record when I return to the grid.
I'd like to use some JS to filter on a key field to reduce the list to the newly added record.
When the record IS NEW and being saved, a rule could set a SessionVar or RegularUser field to some value which can show me the new record (ID, AcctCode, ItemCode, etc. Whatever is needed.) as long as I can fire some JS when I get back to the Grid and insert a filter automatically using my saved value.

[NOTE] This has traditionally been an issue in Aware for years, IMHO, just based on its design and Kendo. If my grid is going to refresh after the new record is added, then the user has no idea or immediate visibility of the newly added record. UNLESS you always sorted it by Date Added DESC, in which case your new record would be at the top. So in a few cases, this will work. But usually the user will have to Sort or filter on something he remembers from the new record to see it in the grid and now edit it. [/NOTE]

customaware

Can you not just set a "NEW" Flag and filter on that and then after some specified time.... such as when the Session ends or if the User Edits the record or at end of day... or whatever.... check the NEW Flags and convert them the "EXISTING"

If you do it like this then there are other nice possibilities. Such as highlight the row as new JUST for this user who added it to save adding another NEW column. If you know what I mean.

Jaymer

customaware
Well, it’s not a bad idea.
But if I’m reading this correctly, when the user initially goes to the customer grid to see if we have Acme Corp., he may or may not find acme Corp. He might’ve filtered on all the As.
At some point, he realizes he needs to add Acme Corp.

So when he comes back to the grid and it refreshes, the old filter is still there (customers starting with A), and now he MIGHT see a row highlighting because this system maintained field says NEW and a row rule highlights all As. Of course that row might be off screen on page 3, and he’s not gonna see it.

(Btw, you showed in Tampa how you speeded up a grid by using JS rules. Do you have a code template you could share? I hate seeing all those lines in the Tomcat Log for all those Applicability rules firing.
Similarly I have one grid with 7 or 8 columns for Row Operations. These eat up horizontal space. I am planning on writing some JS to conditionally hide those columns. I have this working in another BSV for a single column (because I hate wasting row space on a empty column because the button is hidden) . This new adaptation needs to respond to a Panel Filter. If showing OPEN Transactions, then I want 3 buttons showing (ie. Need to hide columns 4,5,6,7) and if showing PAST DUE then a diff set of columns need to be hidden. )

OK, back to the original issue.
If I go to a grid and I know, I need to add a record.
There’s no reason for me to filter to look for a record.
The original problem still stands.
The grid is showing 1 to 20 of 500 records.
I add record 501. And when I come back to the grid, it shows me the first 20 records of 501.
And now the user needs to find the record he just added.
So even if I use your suggested strategy of putting NEW in a particular field, I still need a trigger to refresh the grid and programmatically stuff NEW into the filter column. Back to the original question I was asking.

In magic, I could’ve done a KBPUT and stuffed a control R, the new customer ID, <ENTER> and the screen would redraw.
This is why I just say there’s a shortcoming that’s always been there that makes us have to force to work around for this business case.

Jaymer

Issue restated:

I go to a grid to add a record.
There’s no reason for me to filter to look for a record.
The grid is showing 1 to 20 of 500 records.
I add record 501. Grid refreshes. It shows me the first 20 records of 501.
The user needs to find the record he just added.

I would like to add some JS to set a filter based on a SessionVar variable, which I will set as the new record is being saved. This way, the user quickly and easily sees the newly created record and can continue.

Any ideas?